Slide in.
AI agents invoke vfx_slide_in 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 applies a visual effect (slide-in transition/animation) to video content using MoviePy. It triggers an external video processing operation whose effects depend on arguments. The description is minimal, but in context of a professional video editing server, this executes a video transformation. It's not purely read, and not destructive/financial. Confidence is moderate due to the uninformative description.
From the tool's definition Tool name 'vfx_slide_in' and description 'Slide in.' on a video editing MCP server with 70+ tools for video transformations
Attacks that exploit this kind of access
Slide in. 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_slide_in: 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_slide_in 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_slide_in 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_slide_in. 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_slide_in 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 →