Mark a task as completed in Todoist
AI agents use todoist_close_task 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.
Closing/marking a task as completed is a reversible modification of task state (the task can be reopened). This does not delete data, execute arbitrary code, move money, or trigger external operations—it simply updates a boolean or status field. While it modifies data, the operation is non-destructive and can be undone by reopening the task. This fits the Write category: creates or modifies data reversibly.
From the tool's definition Tool name 'todoist_close_task' and description 'Mark a task as completed in Todoist' indicate a state modification operation that marks a task's completion status.
Attacks that exploit this kind of access
Mark a task as completed in Todoist. 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.
Register the MCP Todoist MCP server in PolicyLayer and add a rule for todoist_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 MCP Todoist. Nothing to install.
todoist_close_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the todoist_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.
Set action: deny in the PolicyLayer policy for todoist_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.
todoist_close_task is provided by the MCP Todoist MCP server (kentaroh7777/mcp-todoist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →