Convert image to animated video
AI agents invoke image_to_video to trigger actions in Ghibli Video MCP Server. 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 an external pipeline that transforms a static image into an animated video using Ghibli-style aesthetics. It is not a simple read or write; it triggers a compute/processing operation with side effects (video generation). It doesn't delete data (not Destructive) or move money (not Financial), so Execute is the most appropriate category.
From the tool's definition "Convert image to animated video" — triggers an external media processing/generation operation
Attacks that exploit this kind of access
Convert image to animated video. It is categorised as a Execute tool in the Ghibli Video MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ghibli Video MCP Server MCP server in PolicyLayer and add a rule for image_to_video: 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 Ghibli Video MCP Server. Nothing to install.
image_to_video 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 image_to_video 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 image_to_video. 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.
image_to_video is provided by the Ghibli Video MCP Server MCP server (michaelyangjson/mcp-ghibli-video). 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 →