gateway_unregister

Remove a registered target (and any routes pointing at it) from the hub.

Server Claude Team MCP lakshan12367/mcp
Category Destructive
Risk class Critical
Parameters 00 required

What gateway_unregister does on Claude Team MCP

AI agents call gateway_unregister 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.

Why gateway_unregister needs a policy

This tool irreversibly deletes gateway registration records and associated routes. Once unregistered, the target and its routes are gone and cannot be recovered without manual re-registration. This is a destructive operation that destroys infrastructure configuration state. While not data deletion in the traditional sense, it permanently removes system configuration, making it more severe than a Write operation.

From the tool's definition Tool name 'gateway_unregister' combined with description 'Remove a registered target (and any routes pointing at it) from the hub' indicates irreversible deletion of gateway configuration state.

Questions about gateway_unregister

What does the gateway_unregister tool do? +

Remove a registered target (and any routes pointing at it) from the hub. 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.

How do I enforce a policy on gateway_unregister? +

Register the Claude Team MCP server in PolicyLayer and add a rule for gateway_unregister: 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.

What risk level is gateway_unregister? +

gateway_unregister is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gateway_unregister? +

Yes. Add a rate_limit block to the gateway_unregister 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.

How do I block gateway_unregister completely? +

Set action: deny in the PolicyLayer policy for gateway_unregister. 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.

What MCP server provides gateway_unregister? +

gateway_unregister 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.