close_task · Todoist MCP Server MCP: Risk & Policy

WHAT IT DOES

What close_task does on Todoist MCP Server

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

WHY IT NEEDS A POLICY

Why close_task needs a policy

Closing a task changes its state from open to completed but is reversible (tasks can be reopened). This is a state modification without permanent data loss or external side effects, placing it in the Write category rather than Destructive. Severity is medium because an agent could inadvertently mark many tasks complete, disrupting a user's task management, but the impact is recoverable.

From the tool's definition Tool description states 'marks as complete and moves to history, or schedules next occurrence for recurring tasks' — this modifies task state reversibly. The action can be undone by reopening the task.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_task Rate-limited

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

FAQ

Questions about close_task

What does the close_task tool do? +

Close a task (marks as complete and moves to history, or schedules next occurrence for recurring tasks). It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_task? +

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

What risk level is close_task? +

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

Can I rate-limit close_task? +

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

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

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