Logical OR of masks.
AI agents invoke vfx_masks_or to trigger actions in vidMagik-mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a video compositing operation (logical OR on masks) within a video editing pipeline. It is not a simple read, nor does it delete or move money. It triggers a processing action whose result depends on the input masks, placing it in the Execute category. Severity is medium given it operates on video data but has limited blast radius compared to destructive or financial operations.
From the tool's definition 'Logical OR of masks' — performs a compositing operation combining mask data, triggering a video processing/transformation operation
Attacks that exploit this kind of access
Logical OR of masks. It is categorised as a Execute tool in the vidMagik-mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the vidMagik- MCP server in PolicyLayer and add a rule for vfx_masks_or: 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_masks_or is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vfx_masks_or 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_masks_or. 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_masks_or 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 →