todoist_add_comment
AI agents use todoist_add_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.
This tool creates new data (a comment on a task) reversibly—comments can be edited or deleted. This is a Write operation. Severity is medium because while comments are not critical data, adding unwanted or spam comments could clutter tasks and require cleanup. The empty description lowers confidence slightly, but the name and server context clearly indicate the function.
From the tool's definition Tool name 'todoist_add_comment' indicates comment creation. Server description states the system supports 'comments' as a managed resource. Adding a comment creates new data in Todoist.
Attacks that exploit this kind of access
todoist_add_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 todoist_add_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.
todoist_add_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 todoist_add_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 todoist_add_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.
todoist_add_comment is provided by the Todoist MCP Server MCP server (shockedrope/todoist-mcp-server). 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 →