get_analytics_group_models
Get a paginated per-model breakdown with total_groups, group_count, and a models array containing request count, cost, and token usage. Use this to compare model cost, popularity, and efficiency; use get_token_analytics or get_cost_analytics for time-series trends instead.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-analytics-group-models.md
What get_analytics_group_models does on Portkey Admin
AI agents call get_analytics_group_models to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_analytics_group_models is rated Low
This tool performs data retrieval and reporting on analytics metrics (request count, cost, token usage) with no side effects. It returns aggregate statistics for comparison purposes. No data is created, modified, deleted, or used to trigger external operations. The classification is Read.
From the tool's definition Tool retrieves analytics data with 'Get a paginated per-model breakdown' and 'a models array containing request count, cost, and token usage'.
Attacks that exploit this kind of access
The rule that runs get_analytics_group_models safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_analytics_group_models, this is the rule to start with:
get_analytics_group_models is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every get_analytics_group_models call is checked against it from then on.
Questions about get_analytics_group_models
Get a paginated per-model breakdown with total_groups, group_count, and a models array containing request count, cost, and token usage. Use this to compare model cost, popularity, and efficiency; use get_token_analytics or get_cost_analytics for time-series trends instead. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for get_analytics_group_models: 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 Admin. Nothing to install.
get_analytics_group_models 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_analytics_group_models 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_analytics_group_models. 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_analytics_group_models is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue