deleteLabel
AI agents call deleteLabel to permanently remove resources in Todoist MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes labels, which is an irreversible action that destroys data. Even though the blast radius is limited to label metadata (not tasks or financial data), deletion operations are categorized as Destructive per the schema hierarchy. High severity because deletion of labels could affect task organization and cannot be undone.
From the tool's definition Tool name is 'deleteLabel' with empty description. The 'delete' prefix indicates irreversible removal of data (labels in Todoist). Sibling context shows destructive operations like 'deleteComment', 'deleteProject', 'deleteSection' on the same server.
Attacks that exploit this kind of access
deleteLabel. It is categorised as a Destructive tool in the Todoist MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for deleteLabel: 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.
deleteLabel 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 deleteLabel 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 deleteLabel. 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.
deleteLabel is provided by the Todoist MCP Server MCP server (stevengonsalvez/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 →