AI agents call get_stale_task_report to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports information about stale tasks. It performs a read-only query operation to identify tasks that have been in progress for longer than expected. There are no side effects, data modifications, deletions, or external operations triggered. The blast radius of misuse is minimal—an agent could only generate a report of stale tasks, which has no destructive or operational consequences.
From the tool's definition Tool name is 'get_stale_task_report' and description states it 'Report[s] stale in_progress tasks with minutes stale.' This is a retrieval/reporting operation that queries task status without modifying data.
Attacks that exploit this kind of access
Report stale in_progress tasks with minutes stale. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for get_stale_task_report: 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 Todos. Nothing to install.
get_stale_task_report 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_stale_task_report 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_stale_task_report. 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_stale_task_report is provided by the Todos MCP server (@hasna/todos). 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 →