Get all active tasks. Can filter by project, label, or Todoist filter string.
AI agents call get_tasks to retrieve information from Todoist MCP Helper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves task data from Todoist without creating, modifying, or deleting any information. It is a read-only operation that queries existing tasks based on filter criteria. The severity is low because misuse would only expose task information already known to the user or accessible through legitimate queries, with no side effects or destructive potential.
From the tool's definition Tool name is 'get_tasks' and description states 'Get all active tasks' with filtering capabilities. These are query/retrieval operations with no modification or deletion of data.
Attacks that exploit this kind of access
Get all active tasks. Can filter by project, label, or Todoist filter string. It is categorised as a Read tool in the Todoist MCP Helper MCP Server, which means it retrieves data without modifying state.
Register the Todoist MCP Helper MCP server in PolicyLayer and add a rule for get_tasks: 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 Helper. Nothing to install.
get_tasks 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_tasks 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_tasks. 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_tasks is provided by the Todoist MCP Helper MCP server (littlepeter52012/todoist-mcp-helper). 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 →