Reopen a previously completed task.
AI agents use reopen_task to create or update resources in Todoist MCP Helper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Helper environment.
This tool modifies task status by changing a completed task back to an active state. While this is a state change, it is fully reversible (the task can be completed again), making it a Write operation rather than Destructive. The impact is limited to a single task's status within a personal task management system, resulting in low severity.
From the tool's definition Tool name 'reopen_task' and description 'Reopen a previously completed task' indicate modification of task state from completed back to active, which is reversible data modification.
Attacks that exploit this kind of access
Reopen a previously completed task. It is categorised as a Write tool in the Todoist MCP Helper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Helper 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 Helper. 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 Helper MCP server (littlepeter52012/todoist-mcp-helper). 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 →