list_active_tasks
AI agents call list_active_tasks 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 and lists active tasks without modifying, deleting, or executing any operations. It has no side effects and poses minimal risk. The absence of a description does not significantly lower confidence because the name is explicitly descriptive of a read operation and is consistent with the server's stated capability to 'list tasks'.
From the tool's definition Tool name 'list_active_tasks' indicates a retrieval operation that queries tasks from Todoist. Server description confirms it 'enables AI agents to create and list tasks' with 'project-based filtering', establishing this as a read-only query.
Attacks that exploit this kind of access
list_active_tasks. 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 list_active_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 Server. Nothing to install.
list_active_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 list_active_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 list_active_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.
list_active_tasks is provided by the Todoist MCP Server MCP server (mehularora8/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 →