AI agents call tool_delete_path to permanently remove resources in UltimateCoder — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of files or directories is an irreversible destructive action that cannot be undone. Even without a description, the semantics of 'delete_path' clearly indicate this tool removes data permanently. Given the server's focus on file handling and terminal operations, this almost certainly deletes local filesystem objects.
From the tool's definition Tool name is 'tool_delete_path' with an empty description. The verb 'delete' combined with 'path' (file system object) indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access tool_delete_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UltimateCoder, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_delete_path:
{
"version": "1",
"default": "deny",
"hide": [
"tool_delete_path"
]
}tool_delete_path 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.
tool_delete_path. It is categorised as a Destructive tool in the UltimateCoder MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UltimateCoder MCP server in PolicyLayer and add a rule for tool_delete_path: 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 UltimateCoder. Nothing to install.
tool_delete_path 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 tool_delete_path 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 tool_delete_path. 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.
tool_delete_path is provided by the UltimateCoder MCP server (m-ahmed-elbeskeri/ultimatecodermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UltimateCoder, 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.
23 UltimateCoder tools catalogued and risk-classified — across an index of 43,000+ MCP servers.