search_projects
AI agents call search_projects 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.
Search operations retrieve and filter data without side effects. The PensionPro server context shows this tool follows a pattern of read-only operations (get_* and search_*) alongside write operations (add_note, create_*, complete_task). Despite missing explicit description, the semantic meaning of 'search' combined with server design patterns indicates data retrieval only.
From the tool's definition Tool name 'search_projects' strongly indicates a search/query operation with no modification capability. No description provided, but name and sibling tools (get_client_details, get_employee_stats, get_notes—all read operations) establish context.
Attacks that exploit this kind of access
search_projects. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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 →