Get cache statistics and performance metrics
AI agents call get_cache_stats to retrieve information from YouTube Transcript DL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns cache statistics—no data is created, modified, deleted, or executed. It has no side effects and poses minimal security risk. The low severity reflects that cache metrics disclosure is typically low-impact information.
From the tool's definition Tool name 'get_cache_stats' and description 'Get cache statistics and performance metrics' indicate a read-only query operation that retrieves metadata about cache performance without modifying any data.
Attacks that exploit this kind of access
Get cache statistics and performance metrics. It is categorised as a Read tool in the YouTube Transcript DL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube Transcript DL MCP Server MCP server in PolicyLayer and add a rule for get_cache_stats: 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 YouTube Transcript DL MCP Server. Nothing to install.
get_cache_stats 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_stats 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_stats. 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_stats is provided by the YouTube Transcript DL MCP Server MCP server (jedarden/yt-transcript-dl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →