delete_directory
AI agents call delete_directory to permanently remove resources in Windows Operations MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete_directory performs irreversible deletion of file system directories and all contents. This cannot be undone and represents maximum blast radius if an AI agent misuses it (e.g., deleting critical system directories, user data, or application files).
From the tool's definition Tool name 'delete_directory' combined with server description stating the tool 'Enables comprehensive Windows system management' including 'file operations.' The function name explicitly indicates directory deletion, which is irreversible.
Attacks that exploit this kind of access
delete_directory. It is categorised as a Destructive tool in the Windows Operations MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Windows Operations MCP server in PolicyLayer and add a rule for delete_directory: 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 Windows Operations MCP. Nothing to install.
delete_directory 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_directory 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_directory. 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_directory is provided by the Windows Operations MCP server (sandraschi/windows-operations-mcp). 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 →