Download a video from any supported platform (YouTube, Vimeo, etc.) to local storage. Returns the file path of the downloaded video.
AI agents use download-video to create or update resources in Video Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Video Toolkit environment.
This tool retrieves a video from an external platform and writes it to local storage. It creates a new file on disk, which is a write operation. It is not purely read (it has a side effect of creating a file), not destructive (it doesn't delete anything), and not financial.
From the tool's definition Download a video from any supported platform (YouTube, Vimeo, etc.) to local storage. Returns the file path of the downloaded video.
Attacks that exploit this kind of access
Download a video from any supported platform (YouTube, Vimeo, etc.) to local storage. Returns the file path of the downloaded video. It is categorised as a Write tool in the Video Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Video Toolkit MCP server in PolicyLayer and add a rule for download-video: 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 Toolkit. Nothing to install.
download-video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the download-video 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 download-video. 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.
download-video is provided by the Video Toolkit MCP server (jamesanz/transcript-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 →