stop · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What stop does on Windows Operations MCP

AI agents invoke stop to trigger actions in Windows Operations MCP. 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 needs a policy

Without an explicit description, classification relies on context: this tool operates within a Windows administration framework centered on PowerShell/CMD execution and system management. 'Stop' most likely triggers termination of processes or services, which constitutes Execute (code/operation triggering) rather than mere Read or Write.

From the tool's definition Tool name 'stop' in a Windows Operations MCP server context with sibling tools like 'cmd', 'agentic_system_hardening', and 'autonomous_troubleshooter'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop Rate-limited

stop 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": {
      "limits": [
        {
          "counter": "stop_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 Windows Operations MCP, so you can run agents against it safely.

FAQ

Questions about stop

What does the stop tool do? +

stop. It is categorised as a Execute tool in the Windows Operations MCP 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? +

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

What risk level is stop? +

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

Can I rate-limit stop? +

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

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

stop is provided by the Windows Operations MCP server (sandraschi/windows-operations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.