task_create · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What task_create does on Windows Operations MCP

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

The tool name 'task_create' strongly suggests creation of Windows Scheduled Tasks, which can execute arbitrary code or scripts at defined times or system events. This is an Execute-category action with high severity since scheduled tasks can be used to persist code execution or trigger system-level operations.

From the tool's definition Tool name 'task_create' on a Windows Operations MCP server that includes PowerShell/CMD execution and system monitoring capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_create Rate-limited

task_create 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_create": {
      "limits": [
        {
          "counter": "task_create_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_create

What does the task_create tool do? +

task_create. 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_create? +

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

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

Can I rate-limit task_create? +

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

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

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