AI agents use archive_project to create or update resources in Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist environment.
Archiving is a reversible operation—archived projects can typically be unarchived. This makes it Write rather than Destructive. However, it removes the project from active view and workflow, affecting project visibility and access. Severity is medium because the action is reversible but impacts project organization and collaboration.
From the tool's definition Tool name 'archive_project' and description 'Archive a project' indicate a state-change operation that marks a project as archived rather than permanently deleting it.
Attacks that exploit this kind of access
Archive a project. It is categorised as a Write tool in the Todoist 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 archive_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. Nothing to install.
archive_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 archive_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 archive_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.
archive_project is provided by the Todoist MCP server (stevengonsalvez/mcp-todoist). 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 →