Get tasks completed within a specific date range
AI agents call get-tasks-completed-by-completion-date to retrieve information from Todoist MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical task completion data filtered by date range. It retrieves information without creating, modifying, deleting, executing code, or moving money. The 'get' verb and read-only nature of fetching completed task metadata with no side effects clearly categorizes this as a Read operation with low severity.
From the tool's definition Tool name 'get-tasks-completed-by-completion-date' and description 'Get tasks completed within a specific date range' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get tasks completed within a specific date range. It is categorised as a Read tool in the Todoist MCP MCP Server, which means it retrieves data without modifying state.
Register the Todoist MCP server in PolicyLayer and add a rule for get-tasks-completed-by-completion-date: 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. Nothing to install.
get-tasks-completed-by-completion-date 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-completed-by-completion-date 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-completed-by-completion-date. 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-completed-by-completion-date is provided by the Todoist MCP server (jdh747/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 →