Get all todo projects. These are like folders for tasks in Todoist
AI agents call get_projects to retrieve information from Todoist Python 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 project metadata from Todoist without modifying, executing code, or causing side effects. It is purely informational, making it a Read category tool with low severity. An agent misusing this tool could only over-query or expose project names, but cannot alter data or trigger external actions.
From the tool's definition Tool name 'get_projects' and description 'Get all todo projects' indicate a retrieval operation. The verb 'get' and the absence of modification language ('create', 'update', 'delete') confirm this is a read-only query.
Attacks that exploit this kind of access
Get all todo projects. These are like folders for tasks in Todoist. It is categorised as a Read tool in the Todoist Python MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todoist Python MCP Server MCP server in PolicyLayer and add a rule for get_projects: 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 Python MCP Server. Nothing to install.
get_projects 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 get_projects 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 get_projects. 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.
get_projects is provided by the Todoist Python MCP Server MCP server (johnxjp/todoist-mcp-python). 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 →