{"version":"2.1.319","anchor":"mcp-connector-denyask-rules-new-name-keys-and-warnings","canonical_anchor":"mcp-connector-denyask-rules-new-name-keys-and-warnings","heading":"Permission rules for claude.ai connectors can use the connector's name","tier":"use","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-connector-denyask-rules-new-name-keys-and-warnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Permission rules for claude.ai connectors can use the connector's name\n\nClaude Code now gives claude.ai connectors a name for deny and ask rules, and warns when a rule written that way cannot apply\n\n**Unclear.** Which situations make a rule written with a connector's claude.ai name fail to apply is not stated.\n\n**What**\n\nMCP servers add tools Claude can use, and claude.ai connectors are MCP servers set up in your claude.ai account. Deny and ask rules are permission rules that block a tool or make Claude ask you first. Claude Code now gives connector tools a name taken from the connector's claude.ai name, and works out which connector a deny rule covers from the connector's ID.\n\nWhen a deny or ask rule written with a connector's claude.ai name will not apply to it, Claude Code logs a warning saying so.\n\n**Why**\n\nYou can write permission rules using the name you see for a connector in claude.ai. The warning tells you when such a rule is not taking effect, so a tool you meant to block or guard is not left open without notice.\n\n- Area: Permissions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}