get_analytics_group_metadata
Get a paginated metadata breakdown with total_groups, group_count, and a metadata_groups array grouped by the required metadata_key. Use this for custom breakdowns like per-environment or per-feature analysis; pass metadata_key in addition to the time window.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-analytics-group-metadata.md
What get_analytics_group_metadata does on Portkey Admin
AI agents call get_analytics_group_metadata 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_metadata is rated Low
This tool retrieves and queries analytics metadata grouped by specified keys for custom analysis (per-environment, per-feature breakdowns). It performs no modifications, deletions, or external operations. The read-only nature of querying analytics data with no side effects clearly classifies this as a Read operation with low severity.
From the tool's definition Tool description states 'Get a paginated metadata breakdown' - retrieves data with no side effects. Returns metadata_groups array, total_groups, and group_count for analytical purposes.
Attacks that exploit this kind of access
The rule that runs get_analytics_group_metadata 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_metadata, this is the rule to start with:
get_analytics_group_metadata 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_metadata call is checked against it from then on.
Questions about get_analytics_group_metadata
Get a paginated metadata breakdown with total_groups, group_count, and a metadata_groups array grouped by the required metadata_key. Use this for custom breakdowns like per-environment or per-feature analysis; pass metadata_key in addition to the time window. 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_metadata: 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_metadata 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_metadata 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_metadata. 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_metadata 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