AI agents call get_user_stats to retrieve information from Pelaris without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation that returns only aggregated statistical counts without accessing individual personal or health data. No data modification, execution, deletion, or financial transaction occurs. The explicit privacy-by-design statement and aggregate-only nature make this a straightforward low-severity read operation with minimal blast radius if misused.
From the tool's definition Tool description states it retrieves 'aggregate user statistics (counts only)' with explicit privacy protection: 'No individual profile data is returned — privacy by design.' The verb 'Get' and nature of aggregate metrics-only retrieval confirm this is a read…
Attacks that exploit this kind of access
Get aggregate user statistics (counts only). No individual profile data is returned — privacy by design. It is categorised as a Read tool in the Pelaris MCP Server, which means it retrieves data without modifying state.
Register the Pelaris MCP server in PolicyLayer and add a rule for get_user_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 Pelaris. Nothing to install.
get_user_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_user_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_user_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_user_stats is provided by the Pelaris MCP server (thedonk/pelaris-mcp-server). 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 →