get_cache_hit_rate
Get cache-effectiveness time-series data with summary.hit_rate, summary.total_hits, summary.total_misses, and per-bucket hits/misses/rate. Use this to measure cache effectiveness; use get_cache_hit_latency for speed rather than hit/miss ratio.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-cache-hit-rate.md
What get_cache_hit_rate does on Portkey Admin
AI agents call get_cache_hit_rate 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_rate is rated Low
This is a read-only query tool that retrieves cache analytics metrics without creating, modifying, deleting, or executing any operations. It falls squarely in the Read category with low severity because misuse would only expose analytics data, not enable destructive or side-effect operations.
From the tool's definition Tool retrieves time-series data and metrics (hit_rate, total_hits, total_misses, per-bucket hits/misses/rate) with no modification of data. Description uses 'Get' and explicitly states 'measure cache effectiveness' indicating a read/analytics operation.
Attacks that exploit this kind of access
The rule that runs get_cache_hit_rate 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_rate, this is the rule to start with:
get_cache_hit_rate 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_rate call is checked against it from then on.
Questions about get_cache_hit_rate
Get cache-effectiveness time-series data with summary.hit_rate, summary.total_hits, summary.total_misses, and per-bucket hits/misses/rate. Use this to measure cache effectiveness; use get_cache_hit_latency for speed rather than hit/miss ratio. 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_rate: 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_rate 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_rate 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_rate. 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_rate 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