get_plan_projects
AI agents call get_plan_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.
This tool appears to retrieve plan project information from the PensionPro API based on its naming convention. Without a description, we cannot confirm it modifies, deletes, or executes operations, so the most conservative classification is Read. The presence of sibling tools with identical 'get_' prefixes (which are clearly read operations) reinforces this assessment.
From the tool's definition Tool name 'get_plan_projects' uses the 'get' verb, which conventionally indicates a retrieval operation. The empty description prevents full certainty, but the naming pattern aligns with other 'get_' tools on this server (get_client_details,…
Attacks that exploit this kind of access
get_plan_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 get_plan_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.
get_plan_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 get_plan_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 get_plan_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.
get_plan_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 →