Remove a registered downstream MCP server.
AI agents call mcp_server_unregister to permanently remove resources in LocalAnt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unregistering an MCP server removes its configuration and access, which cannot be trivially undone—it is a destructive operation that eliminates a capability or resource. While not data deletion per se, it is an irreversible state change. Severity is high because unregistering a server could disrupt workflows or prevent access to legitimate tools, and an AI agent misusing this could disable critical integrations.
From the tool's definition Tool name 'mcp_server_unregister' combined with description 'Remove a registered downstream MCP server' indicates irreversible deletion/removal of server registration state.
Attacks that exploit this kind of access
Remove a registered downstream MCP server. It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalAnt MCP server in PolicyLayer and add a rule for mcp_server_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 LocalAnt. Nothing to install.
mcp_server_unregister 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 mcp_server_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.
Set action: deny in the PolicyLayer policy for mcp_server_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.
mcp_server_unregister is provided by the LocalAnt MCP server (yuga-hashimoto/localant). 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 →