Create a new label with a name and optional color.
AI agents use 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.
This tool creates new data (a label) in a reversible manner. It does not execute code, delete data irreversibly, move money, or retrieve existing data. The blast radius is minimal—a mislabeled label can be easily deleted or modified. Severity is low because label creation has no cascading effects on tasks or critical system state.
From the tool's definition Tool name is 'create_label' and description states 'Create a new label with a name and optional color.' The verb 'create' and the operation of adding a new label to the system indicates a write operation.
Attacks that exploit this kind of access
Create a new label with a name and optional color. 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 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.
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 Server MCP server (strangetoucane/mcp-todoist-mcp). 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 →