{"version":"2.1.251","anchor":"slash-commands-can-be-refused-by-a-live-policy-check","canonical_anchor":"slash-commands-can-be-refused-by-a-live-policy-check","heading":"Slash commands can be refused by a live policy check","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/slash-commands-can-be-refused-by-a-live-policy-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Slash commands can be refused by a live policy check\n\nA slash command can now be refused by a policy attached to it, with the reason shown.\n\n**What**\n\nBefore running a slash command, Claude Code now consults a policy value attached to the command entry and can refuse it, showing the reason. Commands with no such policy value attached still run as before.\n\n**Details**\n\n- The policy value is supplied by the server on each command entry; absent one, the command is allowed.\n- Refusals emit telemetry that separates a stale command list from an active denial.\n\n**Evidence**\n\n`tengu_input_slash_invalid`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}