AI agents use update_label 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.
This tool modifies label data reversibly. It is not destructive (labels are not deleted), not financial, and not execute/code-running. Write category is appropriate for data modification operations. Severity is medium because misuse could alter task organization and label metadata across projects, affecting usability and organization, but the impact is limited to label attributes and reversible.
From the tool's definition Tool name 'update_label' and description 'Update an existing label' indicate modification of existing data.
Attacks that exploit this kind of access
Update an existing label. 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 update_label: 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.
update_label 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 update_label 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 update_label. 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.
update_label is provided by the Todoist MCP server (sjvadrevu/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 →