search_todos
AI agents call search_todos to retrieve information from PensionPro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and context of sibling tools, search_todos most likely retrieves or filters existing todo records without modifying or deleting data. This is a Read operation with low blast radius—the primary risk would be unauthorized information disclosure of pension-related task data.
From the tool's definition Tool name 'search_todos' indicates retrieval of existing todo items. Tool description is empty, but sibling tools on this PensionPro server include 'get_' prefixed read operations (get_client_details, get_employee_stats, get_notes) and task-management tools…
Attacks that exploit this kind of access
search_todos. It is categorised as a Read tool in the PensionPro MCP Server, which means it retrieves data without modifying state.
Register the PensionPro MCP server in PolicyLayer and add a rule for search_todos: 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 PensionPro. Nothing to install.
search_todos 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 search_todos 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 search_todos. 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.
search_todos is provided by the PensionPro MCP server (pypi:pension-pro-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 →