AI agents call delete_build to permanently remove resources in Komodo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations that cannot be undone fall into the Destructive category. While the description is empty, the tool name 'delete_build' combined with context from related tools ('delete_alerter', 'delete_deployment') on the same server clearly indicates this removes build data irreversibly.
From the tool's definition Tool name 'delete_build' indicates irreversible deletion of a build artifact or record. Sibling tools include 'create_build' (Write) and other destructive operations like 'delete_alerter' and 'delete_deployment', confirming the destructive pattern in this…
Documented attack patterns abuse exactly the kind of access delete_build gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_build:
{
"version": "1",
"default": "deny",
"hide": [
"delete_build"
]
}delete_build 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.
delete_build. It is categorised as a Destructive tool in the Komodo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Komodo MCP server in PolicyLayer and add a rule for delete_build: 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. Nothing to install.
delete_build 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_build 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_build. 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_build is provided by the Komodo MCP server (myrikld/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo, 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.
53 Komodo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.