Access detailed information for a specific Todoist task using its unique identifier. Provides complete task metadata including content, description, project and section assignment, due date information, priority level, assigned labels, completion status, parent-child relationships, comments count...
AI agents call get_task 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 purely queries and retrieves task data by identifier. It returns metadata (content, description, dates, labels, timestamps) with no side effects or state changes. This is a straightforward read operation with minimal risk.
From the tool's definition Tool name 'get_task' and description 'Access detailed information for a specific Todoist task' — retrieves task metadata without modification. No creation, deletion, execution, or financial operations.
Documented attack patterns abuse exactly the kind of access get_task gives an agent:
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_task:
{
"version": "1",
"default": "deny",
"tools": {
"get_task": {}
}
}get_task is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Access detailed information for a specific Todoist task using its unique identifier. Provides complete task metadata including content, description, project and section assignment, due date information, priority level, assigned labels, completion status, parent-child relationships, comments count, and timestamps for creation and last modification. 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 get_task: 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.
get_task 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_task 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_task. 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_task 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.
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.