Delete an MCP server from obot by id. Irreversible.
AI agents call delete_mcp_server to permanently remove resources in Obot Admin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of an MCP server configuration, which meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high rather than critical because the blast radius is limited to a single server configuration deletion within the obot gateway infrastructure, though this could disrupt service availability if that…
From the tool's definition Tool description explicitly states 'Delete an MCP server from obot by id. Irreversible.' The term 'Irreversible' combined with 'Delete' directly indicates a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete an MCP server from obot by id. Irreversible. It is categorised as a Destructive tool in the Obot Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obot Admin MCP server in PolicyLayer and add a rule for delete_mcp_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 Obot Admin. Nothing to install.
delete_mcp_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 delete_mcp_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 delete_mcp_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.
delete_mcp_server is provided by the Obot Admin MCP server (kiarashedraki/obot-admin-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 →