kill · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What kill does on Windows Operations MCP

AI agents use kill to create or update resources in Windows Operations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows Operations MCP environment.

WHY IT NEEDS A POLICY

Why kill needs a policy

An AI agent can call kill faster than any human can review — one bad instruction and it creates or modifies resources in Windows Operations MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kill Rate-limited

kill stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kill": {
      "limits": [
        {
          "counter": "kill_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 kill

What does the kill tool do? +

kill. It is categorised as a Write tool in the Windows Operations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kill? +

Register the Windows Operations MCP server in PolicyLayer and add a rule for kill: 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 kill? +

kill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kill? +

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

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

kill 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.