AI agents call delete_deployment to permanently remove resources in Komodo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a deployment, which is an irreversible operation that cannot be undone. Deployments are critical infrastructure components, and their deletion could cause service outages, data loss, and operational disruption. This matches the Destructive category definition of actions that irreversibly delete or overwrite data and cannot be undone.
From the tool's definition Tool name is 'delete_deployment' and description states 'Elimina un deployment de Komodo' (Deletes a deployment from Komodo). The verb 'delete' combined with 'deployment' indicates irreversible removal of infrastructure.
Documented attack patterns abuse exactly the kind of access delete_deployment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_deployment:
{
"version": "1",
"default": "deny",
"hide": [
"delete_deployment"
]
}delete_deployment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Elimina un deployment de Komodo. It is categorised as a Destructive tool in the Komodo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Komodo MCP Server MCP server in PolicyLayer and add a rule for delete_deployment: 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 Komodo MCP Server. Nothing to install.
delete_deployment 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_deployment 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_deployment. 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_deployment is provided by the Komodo MCP Server MCP server (nonetss/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
54 Komodo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.