Get statistics about todos (total, by file, etc.)
AI agents call get_todo_stats to retrieve information from Obsidian Todos 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 aggregates existing todo data to provide summary statistics. It performs no creation, modification, deletion, or execution of external operations. The read-only nature and absence of side effects classify it firmly in the Read category with low severity, as exposure of todo statistics poses minimal security risk.
From the tool's definition get_todo_stats retrieves statistics about todos (total, by file, etc.) with no modification of data. The server description confirms the tool is used to 'retrieve task statistics' via natural language.
Attacks that exploit this kind of access
Get statistics about todos (total, by file, etc.). It is categorised as a Read tool in the Obsidian Todos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Todos 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 Obsidian Todos 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 Obsidian Todos MCP Server MCP server (mtuckerb/obsidian-todos-mcp-server). 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 →