get_employee_stats
AI agents call get_employee_stats 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 employee statistics from the PensionPro pension administration system. As a 'get' operation, it queries/retrieves data without side effects. The sibling tools include other read operations (get_client_details, get_plan_details, get_notes) which suggests this follows the same retrieval pattern. No indication of write, delete, execute, or financial capabilities.
From the tool's definition Tool name 'get_employee_stats' suggests retrieval of statistical data about employees. The 'get_' prefix indicates a read operation with no modification capability. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
get_employee_stats. 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_employee_stats: 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_employee_stats 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_employee_stats 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_employee_stats. 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_employee_stats 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 →