update-section · Todoist MCP: Risk & Policy

WHAT IT DOES

What update-section does on Todoist MCP

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

WHY IT NEEDS A POLICY

Why update-section needs a policy

Section updates in task management systems are reversible modifications—sections can be renamed, reordered, or have properties changed without data loss. This qualifies as Write rather than Destructive (which would apply to delete-section or delete-project also present on this server). Severity is medium because misuse could reorganize task structures confusingly, but changes remain undoable via revert operations.

From the tool's definition Tool description states 'Update a section in Todoist', which modifies existing section data (name, order, etc.) without irreversible deletion. The Todoist API context indicates this performs reversible updates to section metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-section Rate-limited

update-section 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": {
    "update-section": {
      "limits": [
        {
          "counter": "update-section_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 Todoist MCP, so you can run agents against it safely.

FAQ

Questions about update-section

What does the update-section tool do? +

Update a section in Todoist. It is categorised as a Write tool in the Todoist 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 update-section? +

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

What risk level is update-section? +

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

Can I rate-limit update-section? +

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

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

update-section is provided by the Todoist MCP server (jdh747/todoist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.