create_task · Schedule Task MCP: Risk & Policy

WHAT IT DOES

What create_task does on Schedule Task MCP

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

WHY IT NEEDS A POLICY

Why create_task needs a policy

This tool creates new scheduled tasks that trigger automatic AI agent invocations via MCP sampling. While the creation itself is reversible (tasks can be deleted or paused via sibling tools like delete_task and pause_task), the ability to schedule arbitrary code execution without human oversight during trigger events poses a medium severity risk. Misuse could schedule malicious operations to run unattended.

From the tool's definition Tool 'create_task' creates and persists scheduled tasks in SQLite with 'interval, cron, or one-time date trigger'. The description explicitly states the task is persisted, indicating reversible data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_task Rate-limited

create_task 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": {
    "create_task": {
      "limits": [
        {
          "counter": "create_task_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 Schedule Task MCP, so you can run agents against it safely.

FAQ

Questions about create_task

What does the create_task tool do? +

Create a scheduled task with interval, cron, or one-time date trigger. It is categorised as a Write tool in the Schedule Task 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 create_task? +

Register the Schedule Task MCP server in PolicyLayer and add a rule for create_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 Schedule Task MCP. Nothing to install.

What risk level is create_task? +

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

Can I rate-limit create_task? +

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

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

create_task is provided by the Schedule Task MCP server (liao1fan/schedule-task-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.