AI agents call shutdown to permanently remove resources in MCP Windows Desktop Automation — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
A shutdown operation is effectively irreversible in the moment — it terminates all running processes and powers off or restarts the system. In an AutoIt context, this would map to the Shutdown() function which can shut down, restart, or log off the system. The blast radius is critical: misuse would terminate all user sessions, running applications, and potentially cause data loss.
From the tool's definition Tool name is 'shutdown' on a Windows Desktop Automation server wrapping AutoIt functionality. The description is empty and uninformative, but the name strongly implies initiating a system shutdown.
Documented attack patterns abuse exactly the kind of access shutdown gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Windows Desktop Automation, and nothing reaches the server without passing your rules. This is the rule we recommend for shutdown:
{
"version": "1",
"default": "deny",
"hide": [
"shutdown"
]
}shutdown 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.
shutdown. It is categorised as a Destructive tool in the MCP Windows Desktop Automation MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Windows Desktop Automation MCP server in PolicyLayer and add a rule for shutdown: 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 MCP Windows Desktop Automation. Nothing to install.
shutdown 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 shutdown 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 shutdown. 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.
shutdown is provided by the MCP Windows Desktop Automation MCP server (mario-andreschak/mcp-windows-desktop-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Windows Desktop Automation, 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.
50 MCP Windows Desktop Automation tools catalogued and risk-classified — across an index of 43,000+ MCP servers.