Low Risk

get_tasks_by_filter

Retrieve Todoist tasks using advanced filter syntax. Supports powerful filter queries using Todoist

How to control get_tasks_by_filter ↓

What get_tasks_by_filter does on Todoist MCP Server

AI agents call get_tasks_by_filter 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.

Low Risk

Why get_tasks_by_filter needs a policy

This tool only queries and retrieves task data based on filters. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal (information disclosure only), making it a low-severity Read operation.

From the tool's definition Tool name 'get_tasks_by_filter' and description 'Retrieve Todoist tasks' explicitly indicate data retrieval with no modification or deletion.

Documented attack patterns abuse exactly the kind of access get_tasks_by_filter gives an agent:

How to control get_tasks_by_filter

PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tasks_by_filter:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tasks_by_filter": {}
  }
}

get_tasks_by_filter is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Todoist MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_tasks_by_filter

What does the get_tasks_by_filter tool do? +

Retrieve Todoist tasks using advanced filter syntax. Supports powerful filter queries using Todoist. It is categorised as a Read tool in the Todoist MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks_by_filter? +

Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for get_tasks_by_filter: 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.

What risk level is get_tasks_by_filter? +

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

Can I rate-limit get_tasks_by_filter? +

Yes. Add a rate_limit block to the get_tasks_by_filter 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.

How do I block get_tasks_by_filter completely? +

Set action: deny in the PolicyLayer policy for get_tasks_by_filter. 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_tasks_by_filter? +

get_tasks_by_filter is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todoist MCP Server tool call.

Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.