label management for Todoist - create, read, update, delete labels with full CRUD operations
AI agents call todoist_labels to permanently remove resources in Mcp Todoist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports delete operations on labels, which would irreversibly remove labels from Todoist. Since the most severe applicable category is Destructive (due to the delete capability), it is classified as such. Severity is medium because deleting labels affects organization/metadata but not the tasks themselves, limiting the blast radius.
From the tool's definition create, read, update, delete labels with full CRUD operations
Documented attack patterns abuse exactly the kind of access todoist_labels gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Todoist, and nothing reaches the server without passing your rules. This is the rule we recommend for todoist_labels:
{
"version": "1",
"default": "deny",
"hide": [
"todoist_labels"
]
} todoist_labels disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
label management for Todoist - create, read, update, delete labels with full CRUD operations. It is categorised as a Destructive tool in the Mcp Todoist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_labels: 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 Mcp Todoist. Nothing to install.
todoist_labels is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the todoist_labels 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_labels. 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_labels is provided by the Mcp Todoist MCP server (shayonpal/mcp-todoist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Todoist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Mcp Todoist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.