Remove a server from the registry.
AI agents call remove_server to permanently remove resources in SuperMCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on server registry state. While not directly destructive to end-user data, removing a server from the registry cannot be undone through the tool itself and breaks AI agent access to that server's functionality. This constitutes a destructive action on system configuration.
From the tool's definition Tool name is 'remove_server' with description 'Remove a server from the registry.' The action removes a server configuration irreversibly from the registry, preventing future access to that server's capabilities.
Attacks that exploit this kind of access
Remove a server from the registry. It is categorised as a Destructive tool in the SuperMCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SuperMCP Server MCP server in PolicyLayer and add a rule for remove_server: 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 SuperMCP Server. Nothing to install.
remove_server 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 remove_server 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 remove_server. 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.
remove_server is provided by the SuperMCP Server MCP server (yakupatahanov/supermcp). 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 →