Create a new personal label.
AI agents use create_label to create or update resources in Todoist MCP Helper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Helper environment.
This tool creates a new label in Todoist, which is a reversible write operation. Labels are metadata used to organize tasks and can be modified or deleted later. The blast radius is minimal—creating labels has no side effects on tasks, finances, or system operations. It is purely a data creation action with low risk of unintended consequences.
From the tool's definition Tool name is 'create_label' and description states it will 'Create a new personal label.' The verb 'Create' combined with the action of adding a new label indicates data creation.
Attacks that exploit this kind of access
Create a new personal label. It is categorised as a Write tool in the Todoist MCP Helper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Helper MCP server in PolicyLayer and add a rule for 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 Helper. Nothing to install.
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 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 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.
create_label is provided by the Todoist MCP Helper MCP server (littlepeter52012/todoist-mcp-helper). 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 →