todoist_create_label
AI agents use todoist_create_label 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.
Creating a label is a reversible data modification operation (labels can be deleted or modified). It does not execute code, delete data permanently, or move money. This is a standard Write operation with minimal blast radius—a mislabeled task is easily corrected and does not harm system integrity or user data irreversibly.
From the tool's definition Tool name 'todoist_create_label' indicates creation of a label resource. Sibling tools include 'todoist_create_task', 'todoist_create_project', 'todoist_create_section', and 'todoist_complete_task', all of which are Write or task-management operations.
Attacks that exploit this kind of access
todoist_create_label. 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_create_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 MCP Server. Nothing to install.
todoist_create_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 todoist_create_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 todoist_create_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.
todoist_create_label 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 →