Reopens a previously closed (completed) task in Todoist
AI agents use reopen-task 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.
This tool modifies existing data (task status) in a reversible manner. It changes a task's state from closed/completed to open/active, which is a data modification operation. This fits the Write category as it creates or modifies data reversibly. It is not Destructive because the change is reversible (the task can be closed again).
From the tool's definition Tool name is 'reopen-task' and description states it 'Reopens a previously closed (completed) task in Todoist'. This modifies task state by changing a task from completed back to active status.
Attacks that exploit this kind of access
Reopens a previously closed (completed) task 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.
Register the Todoist MCP server in PolicyLayer and add a rule for reopen-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. Nothing to install.
reopen-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 reopen-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 reopen-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.
reopen-task is provided by the Todoist MCP server (scofieldkoh/todoist_mcp). 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 →