fetch_stock_videos
AI agents call fetch_stock_videos to retrieve information from Media-Editor-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'fetch' combined with 'stock_videos' suggests this tool retrieves pre-existing video content from a stock library for use in editing projects. This is a retrieval operation with no destructive, financial, or execution implications. Even though the description is empty, the tool name itself is sufficiently clear. Confidence reduced from 0.95 to 0.85 due to lack of descriptive text confirming non-side-effects.
From the tool's definition Tool name 'fetch_stock_videos' indicates retrieval of video assets; empty description limits confidence but naming suggests querying/fetching data without side effects. Consistent with read operations on a media editing platform.
Attacks that exploit this kind of access
fetch_stock_videos. It is categorised as a Read tool in the Media-Editor-MCP MCP Server, which means it retrieves data without modifying state.
Register the Media-Editor- MCP server in PolicyLayer and add a rule for fetch_stock_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 Media-Editor-MCP. Nothing to install.
fetch_stock_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 fetch_stock_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 fetch_stock_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.
fetch_stock_videos is provided by the Media-Editor- MCP server (nguyenph88/media-editor-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 →