{"version":"2.1.277","anchor":"new-slash-command-relay-refusal-path-for-unverified-slack-tu","canonical_anchor":"new-slash-command-relay-refusal-path-for-unverified-slack-tu","heading":"New slash-command relay refusal path for unverified Slack turns","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-slash-command-relay-refusal-path-for-unverified-slack-tu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New slash-command relay refusal path for unverified Slack turns\n\nSlash commands from unverified Slack messages can now be blocked before relaying\n\n**What**\n\nWhen a message coming through Slack looks like a slash command but didn't go through the existing bridge-slash-override handling and isn't confirmed to be from a verified human Slack user, a new check called `resolveRelaySlashRefusal` now runs and can block the message from being relayed.\n\n**Why**\n\nThis closes a gap where an unverified Slack message could otherwise trigger a slash command, adding a safeguard against unauthorized or spoofed command execution through Slack integrations.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}