Get statistics about pomodoro sessions
AI agents call get_pomodoro_stats to retrieve information from TodoPomo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregate statistics about completed pomodoro sessions without modifying, deleting, or executing operations. It is a straightforward read operation similar to list or fetch operations. Low severity because querying productivity statistics poses minimal security risk—an AI agent cannot cause harm by retrieving this data.
From the tool's definition Tool name 'get_pomodoro_stats' and description 'Get statistics about pomodoro sessions' indicate a data retrieval operation. The verb 'Get' and context of querying historical statistics confirm read-only behavior with no side effects.
Attacks that exploit this kind of access
Get statistics about pomodoro sessions. It is categorised as a Read tool in the TodoPomo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TodoPomo MCP Server MCP server in PolicyLayer and add a rule for get_pomodoro_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 TodoPomo MCP Server. Nothing to install.
get_pomodoro_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 get_pomodoro_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 get_pomodoro_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.
get_pomodoro_stats is provided by the TodoPomo MCP Server MCP server (pratyayrajak/todopomo-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 →