get_rescued_requests_analytics
Get rescued-request time-series data showing requests recovered by retry or fallback handling. Use this only when your configs include resilience features, and use it to measure how often recovery logic saved requests.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-rescued-requests-analytics.md
What get_rescued_requests_analytics does on Portkey Admin
AI agents call get_rescued_requests_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_rescued_requests_analytics is rated Low
The tool is purely informational, retrieving time-series analytics about request recovery. It performs no side effects, creates no data modifications, executes no external operations, and poses minimal risk if misused by an AI agent—at worst, an agent would read analytics it shouldn't have access to.
From the tool's definition 'Get rescued-request time-series data' and 'measure how often recovery logic saved requests' indicate this tool retrieves and queries analytics data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs get_rescued_requests_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_rescued_requests_analytics, this is the rule to start with:
get_rescued_requests_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_rescued_requests_analytics call is checked against it from then on.
Questions about get_rescued_requests_analytics
Get rescued-request time-series data showing requests recovered by retry or fallback handling. Use this only when your configs include resilience features, and use it to measure how often recovery logic saved requests. 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_rescued_requests_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_rescued_requests_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_rescued_requests_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_rescued_requests_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_rescued_requests_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