AI agents call delete_key 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.
Delete operations are irreversible by definition. Even though the description is empty, the tool name 'delete_key' in the context of an AST-based file editor clearly indicates removal of a key-value pair or object property from code. This matches the Destructive category (irreversibly deletes data).
From the tool's definition Tool name is 'delete_key' which indicates deletion/removal of data. Server context shows this is an AST editor that modifies files. The 'delete_*' naming pattern paired with an AST editing context implies irreversible removal of code structure elements.
Documented attack patterns abuse exactly the kind of access delete_key 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_key:
{
"version": "1",
"default": "deny",
"hide": [
"delete_key"
]
}delete_key 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_key. 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_key: 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_key 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_key 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_key. 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_key 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.