Critical Risk →

shutdown_computer

Shutdown and terminate the virtual computer instance.

How to control shutdown_computer ↓

What shutdown_computer does on Computer Use

AI agents call shutdown_computer to permanently remove resources in Computer Use — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why shutdown_computer needs a policy

Shutting down and terminating a virtual computer instance is an irreversible destructive action. Any unsaved state, running processes, or in-progress work would be lost. The word 'terminate' specifically implies the instance is destroyed, not merely paused, making this a Destructive category tool with high severity given the blast radius of losing an entire compute environment.

From the tool's definition 'Shutdown and terminate the virtual computer instance' — terminates the instance irreversibly

Documented attack patterns abuse exactly the kind of access shutdown_computer gives an agent:

How to control shutdown_computer

PolicyLayer is an MCP gateway — it sits between your AI agents and Computer Use, and nothing reaches the server without passing your rules. This is the rule we recommend for shutdown_computer:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "shutdown_computer"
  ]
}

shutdown_computer disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Computer Use — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about shutdown_computer

What does the shutdown_computer tool do? +

Shutdown and terminate the virtual computer instance. It is categorised as a Destructive tool in the Computer Use MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on shutdown_computer? +

Register the Computer Use MCP server in PolicyLayer and add a rule for shutdown_computer: 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 Computer Use. Nothing to install.

What risk level is shutdown_computer? +

shutdown_computer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit shutdown_computer? +

Yes. Add a rate_limit block to the shutdown_computer 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.

How do I block shutdown_computer completely? +

Set action: deny in the PolicyLayer policy for shutdown_computer. 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.

What MCP server provides shutdown_computer? +

shutdown_computer is provided by the Computer Use MCP server (spencerkinney/computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Computer Use tool call.

Start from Computer Use, 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.

15 Computer Use tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.