Remove shared label in Todoist
AI agents call remove-shared-label to permanently remove resources in Todoist MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a label that may be shared across multiple users or tasks in Todoist. Unlike reversible Write operations (add-label), removal of shared labels cannot be easily undone and affects collaborative work. The blast radius extends to all users and tasks using that label. This qualifies as Destructive rather than Write because the operation is fundamentally one-way and impacts shared resources.
From the tool's definition Tool name 'remove-shared-label' uses 'remove', and description states 'Remove shared label in Todoist'. The sibling tool 'delete-label' is also present, confirming deletion semantics.
Attacks that exploit this kind of access
Remove shared label in Todoist. It is categorised as a Destructive tool in the Todoist MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todoist MCP server in PolicyLayer and add a rule for remove-shared-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. Nothing to install.
remove-shared-label 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 remove-shared-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 remove-shared-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.
remove-shared-label is provided by the Todoist MCP server (miottid/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 →