todoist_task_close · Mcp Todoist MCP: Risk & Policy

WHAT IT DOES

What todoist_task_close does on Mcp Todoist

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

WHY IT NEEDS A POLICY

Why todoist_task_close needs a policy

This tool modifies task data by changing its completion status. While it affects data, the action is reversible — closed/completed tasks can be reopened in Todoist. This makes it Write rather than Destructive. The blast radius is low because it only affects task metadata within the user's task management system, not financial data or external systems.

From the tool's definition Tool description states 'Close a task' and 'completes the current occurrence' — these are modifications to task state that are reversible (tasks can be reopened in Todoist).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

todoist_task_close Rate-limited

todoist_task_close 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": {
    "todoist_task_close": {
      "limits": [
        {
          "counter": "todoist_task_close_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 Mcp Todoist, so you can run agents against it safely.

FAQ

Questions about todoist_task_close

What does the todoist_task_close tool do? +

Close a task. For recurring tasks, this completes the current occurrence and schedules the next one. For non-recurring tasks, this is equivalent to completing the task. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todoist_task_close? +

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

What risk level is todoist_task_close? +

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

Can I rate-limit todoist_task_close? +

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

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

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