getComment
AI agents call getComment 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.
This tool retrieves comment data with no modification or deletion capability. Despite the empty description reducing confidence slightly, the naming convention and server context clearly position this as a read-only query operation. The blast radius of misuse is minimal—an agent could retrieve comments it shouldn't see, but cannot create, modify, or delete data.
From the tool's definition Tool name 'getComment' indicates retrieval of comment data. Description is empty, limiting evidence, but the 'get' prefix and parallel sibling tools (createComment, deleteComment) establish a CRUD pattern where 'getComment' retrieves existing comments without…
Attacks that exploit this kind of access
getComment. 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 getComment: 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.
getComment 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 getComment 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 getComment. 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.
getComment is provided by the Todoist MCP Server MCP server (stevengonsalvez/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 →