Complete project management for Todoist - create, read, update, archive, and query projects with metadata support
AI agents use todoist_projects 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.
The tool spans Read (query), Write (create, update), and potentially Destructive (archive) operations. However, archiving in Todoist is reversible (projects can be unarchived), so it qualifies as Write rather than Destructive. The primary concern is that an AI agent could create, modify, or reorganize projects without authorization.
From the tool's definition Tool description states it can 'create, read, update, archive, and query projects' — the write operations (create, update, archive) modify project state reversibly. Archiving is not truly destructive since projects can typically be restored in Todoist.
Documented attack patterns abuse exactly the kind of access todoist_projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Todoist, and nothing reaches the server without passing your rules. This is the rule we recommend for todoist_projects:
{
"version": "1",
"default": "deny",
"tools": {
"todoist_projects": {
"limits": [
{
"counter": "todoist_projects_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} todoist_projects 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.
Complete project management for Todoist - create, read, update, archive, and query projects with metadata support. 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_projects: 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_projects 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_projects 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_projects. 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_projects is provided by the Mcp Todoist MCP server (shayonpal/mcp-todoist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Todoist, 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.
8 Mcp Todoist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.