Remove routing rule(s) matching pattern (and target if given).
AI agents call gateway_remove_route to permanently remove resources in Claude Team MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing routing rules can disrupt agent coordination and task routing in potentially irreversible ways. The word 'remove' indicates deletion of configuration data. If misused, an AI agent could dismantle the routing infrastructure of the entire coordinated team, causing system-wide disruption.
From the tool's definition 'Remove routing rule(s)' — removing routing rules is an irreversible deletion of configuration that affects how agents/traffic are directed across the system
Attacks that exploit this kind of access
Remove routing rule(s) matching pattern (and target if given). It is categorised as a Destructive tool in the Claude Team MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Team MCP server in PolicyLayer and add a rule for gateway_remove_route: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Team MCP. Nothing to install.
gateway_remove_route is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gateway_remove_route rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for gateway_remove_route. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
gateway_remove_route is provided by the Claude Team MCP server (lakshan12367/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →