AI agents call delete_in_body to permanently remove resources in Ast Editor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix establishes this as a destructive operation that removes code from a file body irreversibly. While the empty description reduces confidence slightly, the tool name combined with the server's purpose (editing files via AST) makes it clear this deletes code structures that cannot be undone without version control.
From the tool's definition Tool name is 'delete_in_body' with an empty description. The name explicitly contains 'delete', indicating irreversible data removal. The context shows this is part of an AST-editing server for modifying code files surgically.
Documented attack patterns abuse exactly the kind of access delete_in_body gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ast Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_in_body:
{
"version": "1",
"default": "deny",
"hide": [
"delete_in_body"
]
}delete_in_body 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_in_body. It is categorised as a Destructive tool in the Ast Editor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ast Editor MCP server in PolicyLayer and add a rule for delete_in_body: 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 Ast Editor. Nothing to install.
delete_in_body 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_in_body 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_in_body. 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_in_body is provided by the Ast Editor MCP server (kambleakash0/agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ast Editor, 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.
59 Ast Editor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.