search_contacts
AI agents call search_contacts 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.
The name 'search_contacts' follows a standard read pattern (search = retrieve/query). However, without a description, confidence is reduced. Given the PensionPro context (pension administration), contacts likely include sensitive personal/financial data (employee or beneficiary information), elevating severity from low to medium. No write, execute, or destructive capability is evident from the name alone.
From the tool's definition Tool name 'search_contacts' indicates a query/retrieval operation. No description provided, but context suggests it searches contact data within a pension administration system.
Attacks that exploit this kind of access
search_contacts. 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_contacts: 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_contacts 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_contacts 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_contacts. 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_contacts 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 →