AI agents call todo_stats to retrieve information from Todo MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
todo_stats is a read-only aggregation/summary tool that queries existing todo data to present statistics. It does not create, modify, delete, or execute anything. Severity is low as misuse only reveals task metadata.
From the tool's definition 'summary of workload, priorities, or overdue items' — purely retrieves and aggregates existing todo data with no side effects
Attacks that exploit this kind of access
Use this when the user wants a summary of workload, priorities, or overdue items. It is categorised as a Read tool in the Todo MCP MCP Server, which means it retrieves data without modifying state.
Register the Todo MCP server in PolicyLayer and add a rule for todo_stats: 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 Todo MCP. Nothing to install.
todo_stats 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 todo_stats 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 todo_stats. 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.
todo_stats is provided by the Todo MCP server (peterfabakker/todo-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 →