get_cache_hit_latency
Get cache-hit-only latency time-series data with summary.total_latency, summary.avg_latency, and per-bucket total/avg latency. Use this to evaluate cached-response speed; use get_latency_analytics for all requests.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-cache-hit-latency.md
What get_cache_hit_latency does on Portkey Admin
AI agents call get_cache_hit_latency 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_cache_hit_latency is rated Low
This tool queries and returns analytics data (cache-hit latency metrics and summaries) without modifying, deleting, executing code, or creating side effects. It is a pure read operation for performance analytics monitoring.
From the tool's definition Tool name uses 'get_' prefix and description states it retrieves 'latency time-series data' and 'summary' metrics for analytical purposes.
Attacks that exploit this kind of access
The rule that runs get_cache_hit_latency 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_cache_hit_latency, this is the rule to start with:
get_cache_hit_latency 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_cache_hit_latency call is checked against it from then on.
Questions about get_cache_hit_latency
Get cache-hit-only latency time-series data with summary.total_latency, summary.avg_latency, and per-bucket total/avg latency. Use this to evaluate cached-response speed; use get_latency_analytics for all 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_cache_hit_latency: 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_cache_hit_latency 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_cache_hit_latency 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_cache_hit_latency. 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_cache_hit_latency 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