task_run · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What task_run does on Windows Operations MCP

AI agents invoke task_run 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 task_run needs a policy

task_run almost certainly executes tasks or scripts on the Windows system—either scheduled tasks via Windows Task Scheduler or arbitrary commands. This is an Execute action with high blast radius because task execution can trigger any operation with the permissions of the running process.

From the tool's definition Tool named 'task_run' with no description, on a server described as enabling 'PowerShell/CMD execution' and 'system automation'. Sibling tools include 'cmd' and 'agentic_system_hardening', confirming this server's focus on executing system operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_run Rate-limited

task_run 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": {
    "task_run": {
      "limits": [
        {
          "counter": "task_run_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 task_run

What does the task_run tool do? +

task_run. 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 task_run? +

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

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

Can I rate-limit task_run? +

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

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

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