AI agents call delete_titled to permanently remove resources in Executor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool is designed to delete data irreversibly. Even without specific details on what is deleted, the explicit 'delete' in the name and 'destructive' in the description clearly indicate this performs an irreversible operation that cannot be undone. This is the defining characteristic of the Destructive category.
From the tool's definition Tool name is 'delete_titled' with description stating 'A destructive tool with a title annotation'. The name explicitly contains 'delete' and the description explicitly labels it as 'destructive'.
Documented attack patterns abuse exactly the kind of access delete_titled gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_titled:
{
"version": "1",
"default": "deny",
"hide": [
"delete_titled"
]
}delete_titled 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.
A destructive tool with a title annotation. It is categorised as a Destructive tool in the Executor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Executor MCP server in PolicyLayer and add a rule for delete_titled: 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 Executor. Nothing to install.
delete_titled 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_titled 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_titled. 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_titled is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.