schedule_task · MCP Workspace Server MCP: Risk & Policy

WHAT IT DOES

What schedule_task does on MCP Workspace Server

AI agents invoke schedule_task to trigger actions in MCP Workspace Server. 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 schedule_task needs a policy

This tool schedules arbitrary commands for execution via the system task scheduler. It triggers external operations whose effects entirely depend on the arguments provided. Misuse could result in persistent scheduled tasks running malicious commands, making it high severity.

From the tool's definition Schedule commands to run at specific times using system task scheduler

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_task Rate-limited

schedule_task 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": {
    "schedule_task": {
      "limits": [
        {
          "counter": "schedule_task_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 Workspace Server, so you can run agents against it safely.

FAQ

Questions about schedule_task

What does the schedule_task tool do? +

Schedule commands to run at specific times using system task scheduler. It is categorised as a Execute tool in the MCP Workspace Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on schedule_task? +

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

What risk level is schedule_task? +

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

Can I rate-limit schedule_task? +

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

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

schedule_task is provided by the MCP Workspace Server MCP server (shayyeffet/ultimate_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.