Permanently delete a comment by its unique identifier. This action will remove the comment from its associated task or project. This operation cannot be undone, so use with caution. Returns confirmation of successful deletion or failure notification.
AI agents call delete_comment 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 description explicitly states it performs permanent deletion that cannot be undone, which is the defining characteristic of the Destructive category. While the blast radius is somewhat limited (deleting a single comment rather than a project or task), the irreversible nature and explicit warning about inability to undo the operation clearly indicate Destructive severity.
From the tool's definition Permanently delete a comment by its unique identifier. This action will remove the comment from its associated task or project. This operation cannot be undone, so use with caution.
Documented attack patterns abuse exactly the kind of access delete_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_comment:
{
"version": "1",
"default": "deny",
"hide": [
"delete_comment"
]
} delete_comment 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.
Permanently delete a comment by its unique identifier. This action will remove the comment from its associated task or project. This operation cannot be undone, so use with caution. Returns confirmation of successful deletion or failure notification. 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 delete_comment: 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.
delete_comment 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 delete_comment 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 delete_comment. 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.
delete_comment is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Todoist MCP Server, 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.
32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.