Searches for videos based on various filters, e.g.
AI agents call search_videos to retrieve information from Video Metadata MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (video metadata filtered by various criteria) with no side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could retrieve unwanted metadata but cannot alter the database or trigger external operations. This is a standard read/query operation typical of data retrieval interfaces.
From the tool's definition Tool name 'search_videos' and description states it 'Searches for videos based on various filters' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Searches for videos based on various filters, e.g. It is categorised as a Read tool in the Video Metadata MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Video Metadata MCP Server MCP server in PolicyLayer and add a rule for search_videos: 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 Video Metadata MCP Server. Nothing to install.
search_videos 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 search_videos 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 search_videos. 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.
search_videos is provided by the Video Metadata MCP Server MCP server (stich-studios/metadata-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 →