todoist_update_project
AI agents use todoist_update_project 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.
The 'update' action modifies project data reversibly (projects can be updated again or reverted), making it a Write category tool rather than Read or Destructive. Severity is medium because project updates could affect task organization and visibility for users, but changes are non-destructive and reversible.
From the tool's definition Tool named 'todoist_update_project' with 'update' verb indicates modification of existing data. Server description states it 'Supports comprehensive task operations including creation, updates, completion, and organization.' Sibling tools include create,…
Attacks that exploit this kind of access
todoist_update_project. 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 todoist_update_project: 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.
todoist_update_project 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_update_project 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_update_project. 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_update_project is provided by the Todoist MCP Server MCP server (shockedrope/todoist-mcp-server). 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 →