// MCP TOOL REFERENCE

orgo_restart_computer

ServerOrgo MCP Server
CategoryDestructive

WHAT IT DOES

What orgo_restart_computer does on Orgo MCP Server

AI agents call orgo_restart_computer to permanently remove resources in Orgo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why orgo_restart_computer needs a policy

The tool explicitly self-describes as destructive, interrupting running processes and losing unsaved state. A restart is irreversible in terms of lost in-memory state and terminated processes, making it Destructive. High severity because misuse on a production VM could terminate critical workloads and cause data loss.

From the tool's definition Destructive: interrupts running processes and unsaved state

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

POLICY

How to control orgo_restart_computer

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "orgo_restart_computer"
  ]
}

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

Create a free account and register Orgo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Orgo MCP Server tools

Destructive orgo_delete_computer Permanently delete a computer and all its data. Cannot be undone. Use only when explicitly Destructive orgo_delete_workspace Permanently delete a workspace and all of its computers. Cannot be undone. Use only when e Execute orgo_bash Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallba Execute orgo_ensure_running Ensure a computer is running. Resumes suspended VMs automatically. Idempotent. Use before Execute orgo_exec Execute Python code on the computer. Returns output or error details. Use for computation, Execute orgo_wait Pause execution on the VM for a fixed duration. Useful for sequencing actions between scre Execute orgo_click Click at pixel (x, y) coordinates on the VM display. Coordinates are in 1280x720 model spa Execute orgo_drag Drag from (start_x, start_y) to (end_x, end_y). Coordinates in 1280x720 model space. Use f

All 28 Orgo MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Orgo MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about orgo_restart_computer

What does the orgo_restart_computer tool do? +

Restart a computer. Useful for recovering from unresponsive states. Use when commands hang, the VM is in a bad state, or after kernel/system config changes that need a boot. Destructive: interrupts running processes and unsaved state. It is categorised as a Destructive tool in the Orgo MCP Server 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 orgo_restart_computer? +

Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_restart_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 Orgo MCP Server. Nothing to install.

What risk level is orgo_restart_computer? +

orgo_restart_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 orgo_restart_computer? +

Yes. Add a rate_limit block to the orgo_restart_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 orgo_restart_computer completely? +

Set action: deny in the PolicyLayer policy for orgo_restart_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 orgo_restart_computer? +

orgo_restart_computer is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orgo MCP Server tool call.

Start from Orgo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.