Add a comment to a task or project
AI agents use add-comment to create or update resources in Todoist MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP environment.
Adding a comment creates new data within Todoist but does not modify existing task/project structure irreversibly, execute code, move money, or delete anything. It is a straightforward Write operation with minimal blast radius—worst case, an unwanted comment is added but can be removed. Severity is low because commenting has no significant downstream effects on task execution or financial systems.
From the tool's definition Tool description states 'Add a comment to a task or project' — the word 'Add' indicates creation of new data (a comment). This is a reversible write operation; comments can be deleted (as evidenced by the sibling tool 'delete-comment').
Attacks that exploit this kind of access
Add a comment to a task or project. It is categorised as a Write tool in the Todoist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP server in PolicyLayer and add a rule for 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. Nothing to install.
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 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 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.
add-comment is provided by the Todoist MCP server (jdh747/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 →