Update an existing comment
AI agents use todoist_comment_update to create or update resources in Mcp Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Todoist environment.
This tool modifies an existing comment in Todoist, which is a reversible write operation. Users can update comments, and the action can be undone or corrected by subsequent updates. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or read-only (Read).
From the tool's definition Tool name 'todoist_comment_update' and description 'Update an existing comment' indicate modification of existing data. Update is a write operation that reversibly modifies content without deletion.
Attacks that exploit this kind of access
Update an existing comment. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_comment_update: 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_comment_update 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 todoist_comment_update 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_comment_update. 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_comment_update is provided by the Mcp Todoist MCP server (@greirson/mcp-todoist). 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 →