AI agents call processClose 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.
AutoIt's ProcessClose function forcibly terminates a running process, which is an irreversible action — it cannot be undone once the process is killed. Any unsaved data in that process would be lost. The description is empty, so confidence is reduced, but the tool name strongly implies process termination, which is destructive in nature. Severity is high because misuse could kill critical system or user processes.
From the tool's definition Tool name 'processClose' on a Windows desktop automation server wrapping AutoIt functionality
Documented attack patterns abuse exactly the kind of access processClose 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 processClose:
{
"version": "1",
"default": "deny",
"hide": [
"processClose"
]
}processClose 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.
processClose. 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 processClose: 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.
processClose 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 processClose 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 processClose. 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.
processClose 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.