Add a comment to a project in Todoist
AI agents use add-comment-to-project 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.
This tool creates new data (a comment) in Todoist but does not delete or irreversibly modify existing data. Comments are typically non-critical metadata and the change is reversible. The blast radius of accidental misuse is minimal—adding unwanted comments to a project is easily correctable.
From the tool's definition Tool name 'add-comment-to-project' and description 'Add a comment to a project in Todoist' indicate creation of new comment data. The action is reversible (comments can be deleted via 'delete-comment' tool on the same server).
Attacks that exploit this kind of access
Add a comment to a project in Todoist. 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-to-project: 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-to-project 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-to-project 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-to-project. 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-to-project is provided by the Todoist MCP server (scofieldkoh/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 →