taskCreateSimple · Routine MCP: Risk & Policy

WHAT IT DOES

What taskCreateSimple does on Routine

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

WHY IT NEEDS A POLICY

Why taskCreateSimple needs a policy

Creating a task is a reversible write operation that modifies the user's task management state. Severity is medium because misuse could clutter or spam the task list, but tasks can be deleted and the impact is limited to the user's own workspace. Not Execute because it doesn't run external commands or scripts; not Destructive because task creation is reversible.

From the tool's definition Tool name 'taskCreateSimple' with description 'Create a task' indicates data creation. The instruction to pass only the 'title' and avoid 'integration_id' or 'distant_task_id' confirms it creates new task records without deletion or irreversible modifications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taskCreateSimple Rate-limited

taskCreateSimple 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": {
    "taskCreateSimple": {
      "limits": [
        {
          "counter": "taskcreatesimple_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 Routine, so you can run agents against it safely.

FAQ

Questions about taskCreateSimple

What does the taskCreateSimple tool do? +

Create a task (simplified for MCP). Usually you only need to pass the title. Do not try to pass the integration_id or distant_task_id. It is categorised as a Write tool in the Routine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on taskCreateSimple? +

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

What risk level is taskCreateSimple? +

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

Can I rate-limit taskCreateSimple? +

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

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

taskCreateSimple is provided by the Routine MCP server (routineco/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.