get-project-comments

// WHEN AI AGENTS USE THIS TOOL

AI agents call get-project-comments to retrieve information from Todoist Integration Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON GET-PROJECT-COMMENTS

Even though get-project-comments only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

doist-todoist-mcp.yaml

tools:
  get-project-comments:
    rules:
      - action: allow

See the full Todoist Integration Server policy for all 39 tools.

// DETAILS

Tool Name get-project-comments

Category Read

MCP Server Todoist Integration Server MCP Server

Risk Level Low

// MORE TODOIST INTEGRATION SERVER TOOLS

Destructive delete-comment Destructive delete-label Destructive delete-project Destructive delete-section Destructive delete-task Destructive remove-shared-label Write add-comment Write add-label

View all 39 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like get-project-comments have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the get-project-comments tool do? +

Get comments from a project in Todoist. It is categorised as a Read tool in the Todoist Integration Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-project-comments? +

Add a rule in your Intercept YAML policy under the tools section for get-project-comments. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Todoist Integration Server MCP server.

What risk level is get-project-comments? +

get-project-comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-project-comments? +

Yes. Add a rate_limit block to the get-project-comments rule in your Intercept 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.

How do I block get-project-comments completely? +

Set action: deny in the Intercept policy for get-project-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.

What MCP server provides get-project-comments? +

get-project-comments is provided by the Todoist Integration Server MCP server (Doist/todoist-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Todoist Integration Server