Time mirror.
AI agents use vfx_time_mirror 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.
This tool modifies video content by reversing or mirroring time (common effect in video editing). The transformation is reversible—the original source remains unchanged and the effect can be undone or reapplied differently. This qualifies as Write (creates/modifies data reversibly) rather than Execute, as it applies a specific deterministic transformation rather than executing arbitrary code.
From the tool's definition Tool name 'vfx_time_mirror' and description 'Time mirror' indicate a video effect that modifies temporal properties of video content. Context of video editing/compositing server confirms this creates a transformed video output.
Attacks that exploit this kind of access
Time mirror. 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_time_mirror: 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_time_mirror 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_time_mirror 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_time_mirror. 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_time_mirror 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 →