Reopen a previously completed Todoist task, returning it to active status. This action restores the task to its previous state before completion, making it available for further work. All task metadata, labels, due dates, and assignments are preserved. Returns the reopened task object with update...
AI agents use reopen_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.
Reopening a task modifies its status reversibly—the task state can be toggled back to completed if needed. This is a write operation that changes data but does not destructively remove or irreversibly delete information. The blast radius is limited to a single task's status field, posing minimal risk even if an AI agent misuses it.
From the tool's definition Tool description states it 'reopen[s] a previously completed Todoist task, returning it to active status' and 'restores the task to its previous state before completion' with 'metadata, labels, due dates, and assignments preserved.' This is a reversible…
Documented attack patterns abuse exactly the kind of access reopen_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reopen_task:
{
"version": "1",
"default": "deny",
"tools": {
"reopen_task": {
"limits": [
{
"counter": "reopen_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reopen_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.
Free to start. No card required.
Reopen a previously completed Todoist task, returning it to active status. This action restores the task to its previous state before completion, making it available for further work. All task metadata, labels, due dates, and assignments are preserved. Returns the reopened task object with updated status. 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.
Register the Todoist MCP Server 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 Server. 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 MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.