Load a video file.
AI agents call video_file_clip to retrieve information from vidMagik-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads a video file into memory for further processing. It retrieves existing data without modifying, deleting, or executing anything. The severity is low as it only accesses local files, though it could potentially read sensitive video content.
From the tool's definition 'Load a video file' — reading/loading a file from disk with no side effects described
Attacks that exploit this kind of access
Load a video file. It is categorised as a Read tool in the vidMagik-mcp MCP Server, which means it retrieves data without modifying state.
Register the vidMagik- MCP server in PolicyLayer and add a rule for video_file_clip: 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 vidMagik-mcp. Nothing to install.
video_file_clip 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 video_file_clip 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 video_file_clip. 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.
video_file_clip is provided by the vidMagik- MCP server (vizionik25/vidmagik-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 →