Retrieve detailed analytics data about user activity within a specified time range, including request counts and costs
AI agents call get_user_stats to retrieve information from Portkey MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches and queries existing analytics data about user activity and costs without modifying state, executing code, deleting data, or moving money. This is a classic read operation with minimal risk.
From the tool's definition Tool name is 'get_user_stats' and description states 'Retrieve detailed analytics data' — retrieve is a read-only operation. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
Retrieve detailed analytics data about user activity within a specified time range, including request counts and costs. It is categorised as a Read tool in the Portkey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Portkey MCP Server 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 Portkey MCP Server. 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 Portkey MCP Server MCP server (r-huijts/portkey-admin-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 →