// SCAN REPORT

Routine

Q: How do I prevent bulk modifications through Routine?

The Routine server has 4 write tools including taskComplete, taskCreateSimple, taskUncomplete. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Routine.

Q: How many tools does the Routine MCP server expose?

18 tools across 2 categories: Read, Write. 14 are read-only. 4 can modify, create, or delete data.

Q: How do I enforce a policy on Routine?

Register the Routine MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

18 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

4 can modify or destroy data

14 read-only

18 tools total

Community server · catalogue entry verified 29/06/2026

How to control Routine ↓

TOOL MAP

What Routine exposes to your agents

Read (14) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Routine tools

Write · Low taskComplete Completing a task modifies task status/state data but does not delete or destroy the task, nor does it execute arbitrary code or move money. Write · Medium taskCreateSimple Creating a task is a reversible write operation that modifies the user's task management state. Write · Medium taskUncomplete The tool explicitly modifies task state (setting a task back to incomplete), which is a reversible write action. Write · Medium taskUpdate The tool updates task data without deleting it or executing external code.

4 of Routine's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Routine

PolicyLayer is an MCP gateway — it sits between your AI agents and Routine, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "taskComplete": {
    "limits": [
      {
        "counter": "taskcomplete_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "authProfile": {
    "limits": [
      {
        "counter": "authprofile_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Routine — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ROUTINE →

Instant setup, no code required.

FULL CATALOGUE

All 18 Routine tools

WRITE 4 tools

Write taskComplete Complete a task. Write taskCreateSimple Create a task (simplified for MCP). Usually you only need to pass the title. Do not try to pass the integratio Write taskUncomplete Uncomplete a task. Write taskUpdate Patch a task.

READ 14 tools

Read authProfile Main user identity. Read calendarAll All calendars. Read calendarGet A calendar. Read eventDay The events on a given day. Read eventGet An event. Read eventTimeline Agenda view for a day. Read pageAll All pages. Read pageGet Get a page. Read peopleByEmail The potential contact owning this email address. Read peopleGet The contact with the given id. Read taskDay Tasks of a day sorted by: starred < default < (completed or ignored). Read taskGet A task. Read taskUnplanned Unplanned tasks. Read taskUpcoming Non-allocated organized by week and sorted alphabetically.

FAQ

Questions about Routine

How do I prevent bulk modifications through Routine? +

The Routine server has 4 write tools including taskComplete, taskCreateSimple, taskUncomplete. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Routine.

How many tools does the Routine MCP server expose? +

18 tools across 2 categories: Read, Write. 14 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Routine? +

Register the Routine MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Routine tool call.

Deterministic rules across all 18 Routine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ROUTINE →

Instant setup, no code required.

18 Routine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.