stop_vm · Mcp Utm MCP: Risk & Policy

WHAT IT DOES

What stop_vm does on Mcp Utm

AI agents invoke stop_vm to trigger actions in Mcp Utm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_vm needs a policy

Stopping a VM is an active control operation that halts a running system. While not destructive (the VM persists; data is not deleted), it is an Execute action because it triggers an external operation whose effects (VM shutdown) depend on which VM argument is provided and could disrupt services, workloads, or agent tasks relying on that VM.

From the tool's definition Tool performs 'Stop a running VM' — a control operation that triggers external state changes on macOS virtual machines via AppleScript, affecting the VM's operational status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_vm Rate-limited

stop_vm stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_vm": {
      "limits": [
        {
          "counter": "stop_vm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Utm, so you can run agents against it safely.

FAQ

Questions about stop_vm

What does the stop_vm tool do? +

Stop a running VM. It is categorised as a Execute tool in the Mcp Utm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_vm? +

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

What risk level is stop_vm? +

stop_vm is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_vm? +

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

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

stop_vm is provided by the Mcp Utm MCP server (neverprepared/mcp-utm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.