Search PensionPro API endpoints by keyword. Use this to discover available API paths.
AI agents call search_api_paths 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.
This tool retrieves metadata about available API endpoints—a read-only discovery mechanism. It does not execute queries, modify data, delete anything, or commit financial transactions. The blast radius is minimal; misuse would reveal API structure but not expose sensitive pensioner data or cause operational harm.
From the tool's definition Tool name 'search_api_paths' and description 'Search PensionPro API endpoints by keyword. Use this to discover available API paths' indicate a search/discovery operation with no data modification or execution of business logic.
Attacks that exploit this kind of access
Search PensionPro API endpoints by keyword. Use this to discover available API paths. 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_api_paths: 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_api_paths 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_api_paths 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_api_paths. 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_api_paths 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 →