task_delete
AI agents call task_delete 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.
Deletion of scheduled tasks cannot be undone without restoring from backups or manually recreating them. This is an irreversible data/configuration destruction operation on a critical system component. Although the description is empty (reducing confidence slightly), the name and server context provide sufficient evidence that this tool removes Windows tasks permanently.
From the tool's definition Tool name 'task_delete' on a Windows Operations MCP server that provides 'comprehensive Windows system management' and 'PowerShell/CMD execution' indicates deletion of Windows scheduled tasks.
Attacks that exploit this kind of access
task_delete. 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 task_delete: 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.
task_delete 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 task_delete 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 task_delete. 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.
task_delete 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 →