todoist_get_comments
AI agents call todoist_get_comments to retrieve information from Todoist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix indicates data retrieval without modification. Retrieving comments from Todoist tasks is a non-destructive, non-financial read operation. No side effects or state changes occur. The tool description is empty, but the naming convention and context from sibling tools provide high confidence in classification.
From the tool's definition Tool name 'todoist_get_comments' indicates a retrieval operation (get). Sibling tools include read operations like 'todoist_list_labels', 'todoist_list_projects', 'todoist_list_sections', and 'todoist_list_tasks' that follow the same naming pattern and are…
Attacks that exploit this kind of access
todoist_get_comments. It is categorised as a Read tool in the Todoist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for todoist_get_comments: 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_get_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the todoist_get_comments 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_get_comments. 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_get_comments 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 →