Update a comment
AI agents use update_comment to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.
Updating a comment modifies data but is reversible—the original content can be restored if needed. This is a Write category action. Severity is medium because an AI agent could modify task comments to introduce false information, mislead task collaborators, or alter project documentation, but the impact is limited to comment content within a single task management system.
From the tool's definition Tool name 'update_comment' and description 'Update a comment' indicate modification of existing data. The server description confirms CRUD operations are supported, and update is a reversible write operation.
Attacks that exploit this kind of access
Update a comment. It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_comment 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 update_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 update_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.
update_comment is provided by the Todoist MCP Server MCP server (rfbatista/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 →