get_most_replayed
AI agents call get_most_replayed to retrieve information from Youtube Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-computed data about video playback patterns and highlights. It queries existing information without creating, modifying, deleting, or executing external operations. The empty description introduces minor uncertainty, but the name and server purpose strongly indicate a read-only data retrieval function consistent with the other informational tools on this server.
From the tool's definition Tool name 'get_most_replayed' suggests retrieving data about frequently replayed moments; server context indicates it surfaces 'most-replayed moments' for analysis.
Attacks that exploit this kind of access
get_most_replayed. It is categorised as a Read tool in the Youtube Context MCP Server, which means it retrieves data without modifying state.
Register the Youtube Context MCP server in PolicyLayer and add a rule for get_most_replayed: 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 Context. Nothing to install.
get_most_replayed 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_most_replayed 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_most_replayed. 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_most_replayed is provided by the Youtube Context MCP server (realiti4/youtube-context-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 →