delete_in_body
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 in the context of an AST code editor, alongside sibling destructive tools like 'delete_key' and 'delete_symbol', indicates this tool removes content from within a code body (e.g., function body, class body). Such edits to source code are effectively irreversible without version control. Severity is high due to the blast radius of deleting code structures across a codebase.
From the tool's definition Tool name 'delete_in_body' combined with sibling tools 'delete_key' and 'delete_symbol' strongly implies irreversible deletion of content within a code body structure. The description is empty, lowering confidence.
Attacks that exploit this kind of access
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/ast-editor). 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 →