get_tasks

ServerTodoist MCP Server
CategoryRead

WHAT IT DOES

What get_tasks does on Todoist MCP Server

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

THE RISK

Low Risk

Why get_tasks needs a policy

This tool retrieves and queries task data without creating, modifying, deleting, or executing operations. It has no side effects on the system state. While it may return sensitive metadata about tasks (dates, priorities, labels), the read-only nature and absence of any write/destructive operations place it firmly in the Read category with low severity—the main risk is information disclosure if unauthorized access…

From the tool's definition Tool description explicitly states it 'Retrieve[s] Todoist tasks' and 'Returns a comprehensive list of tasks' with no mention of modification, deletion, or side effects. The verb 'Retrieve' and passive data retrieval pattern confirm read-only behavior.

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

POLICY

How to control get_tasks

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:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tasks": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Todoist MCP Server tools

Destructive delete_comment Permanently delete a comment by its unique identifier. This action will remove the comment Destructive delete_label PERMANENTLY delete a personal label by its ID. WARNING: This action is IRREVERSIBLE and wi Destructive delete_project Permanently delete a Todoist project by its unique identifier. This action will remove the Destructive delete_section Permanently delete a Todoist section by its unique identifier. This action will remove the Destructive delete_task Permanently delete a Todoist task by its unique identifier. This action will remove the ta Write close_task Mark a Todoist task as completed. This action moves the task to the completed state while Write create_label Create a new personal label with customizable properties including name, color, display or Write create_project Create a new Todoist project with customizable settings. Allows you to set up a project wi

All 32 Todoist MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_tasks

What does the get_tasks tool do? +

Retrieve Todoist tasks with flexible filtering options. Can filter by project, section, labels, or use custom Todoist filter queries. Returns a comprehensive list of tasks with their metadata including content, description, project assignment, due dates, priority levels, labels, completion status, and hierarchy information. Without filters, returns all tasks accessible to the authenticated user. 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? +

Register the Todoist MCP Server 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 Server. Nothing to install.

What risk level is get_tasks? +

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

Can I rate-limit get_tasks? +

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.

How do I block get_tasks completely? +

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.

What MCP server provides get_tasks? +

get_tasks 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.

CHECK YOUR STACK →

Free to start. No card required.

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