{"version":"2.1.301","anchor":"remoteccr-mcp-url-matching-for-deny-lists-plus-a-stricter-t","canonical_anchor":"remoteccr-mcp-url-matching-for-deny-lists-plus-a-stricter-t","heading":"Organization MCP rules now cover remote session servers more closely","tier":"notice","area":"MCP","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/remoteccr-mcp-url-matching-for-deny-lists-plus-a-stricter-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Organization MCP rules now cover remote session servers more closely\n\nOrganization MCP deny lists now match more forms of a remote server's address, and claude-code-remote is limited to four tools\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools, and organizations can set a policy that blocks some of them. When Claude Code checks a remote server against that block list, it now also checks other forms of the server's address, including its hostname and api.anthropic.com.\n\nUnder your organization's MCP policy, the claude-code-remote server now offers only four tools:\n\n- `add_repo`\n\n- `check_repo_access`\n\n- `list_repos`\n\n- `register_repo_root`\n\nThis applies in remote sessions, where `CLAUDE_CODE_REMOTE` is set.\n\n**Why**\n\nThis tightens how an organization's MCP policy is enforced in remote sessions.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}