Resize clip.
AI agents use vfx_resize to create or update resources in vidMagik-mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your vidMagik-mcp environment.
Resizing a video clip modifies its properties (width, height, or aspect ratio) but does not delete data or execute arbitrary code. The operation is reversible, placing it in the Write category rather than Execute or Destructive. Severity is medium because a misused resize could distort content or impact downstream processing, but the effect is not irreversible and does not involve code execution or data destruction.
From the tool's definition Tool name 'vfx_resize' and description 'Resize clip' indicate modification of video clip dimensions. This is a write operation that transforms video data reversibly—resizing can be undone by resizing again to original dimensions.
Attacks that exploit this kind of access
Resize clip. It is categorised as a Write tool in the vidMagik-mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the vidMagik- MCP server in PolicyLayer and add a rule for vfx_resize: 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.
vfx_resize 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 vfx_resize 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 vfx_resize. 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.
vfx_resize 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 →