Get statistics about todos (total, completed, pending, completion rate)
AI agents call get_todo_stats to retrieve information from Sidvy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns aggregated data about todo items. It performs no create, update, delete, or execute operations. The information retrieved is read-only and does not alter any state in the Sidvy system. Statistics gathering is a classic Read category operation with minimal risk.
From the tool's definition Tool retrieves statistics about todos (total, completed, pending, completion rate) with no modification or deletion capability. The verb 'Get' and the nature of statistics gathering indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Get statistics about todos (total, completed, pending, completion rate). It is categorised as a Read tool in the Sidvy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for get_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 Sidvy MCP Server. Nothing to install.
get_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 get_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 get_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.
get_todo_stats is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-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 →