get_error_analytics
Get error-count time-series data with summary.total_errors and per-bucket counts. Use this for high-level error trends; use get_error_rate_analytics for percentages, or get_error_status_codes_analytics and get_error_stacks_analytics for breakdowns.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-error-analytics.md
What get_error_analytics does on Portkey Admin
AI agents call get_error_analytics 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_error_analytics is rated Low
This tool performs data retrieval and aggregation operations on existing analytics data. It returns read-only summaries and metrics without creating, modifying, deleting, or executing any operations. The explicit mention of 'Get' and the analytical purpose confirm this is a Read category tool with low severity, as an AI agent misusing it would only retrieve existing error metrics without side effects.
From the tool's definition Tool retrieves and queries time-series error analytics data with counts and summaries ('Get error-count time-series data with summary.total_errors and per-bucket counts').
Attacks that exploit this kind of access
The rule that runs get_error_analytics 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_error_analytics, this is the rule to start with:
get_error_analytics 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_error_analytics call is checked against it from then on.
Questions about get_error_analytics
Get error-count time-series data with summary.total_errors and per-bucket counts. Use this for high-level error trends; use get_error_rate_analytics for percentages, or get_error_status_codes_analytics and get_error_stacks_analytics for breakdowns. 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_error_analytics: 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_error_analytics 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_error_analytics 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_error_analytics. 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_error_analytics 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