AI agents use create_video to create or update resources in Sora2 MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sora2 MCP environment.
This tool initiates a video generation job, which is a creation operation. It creates a new resource (video generation job) reversibly — the job can be deleted or abandoned. It does not execute arbitrary code, destroy data, or move money. The severity is medium because misuse could incur API costs by spawning many generation jobs, but it is not directly financial or destructive.
From the tool's definition Start a new video generation job with Sora. Returns a job object with status.
Attacks that exploit this kind of access
Start a new video generation job with Sora. Returns a job object with status. Poll get_video_status or use webhooks to monitor completion. It is categorised as a Write tool in the Sora2 MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sora2 MCP server in PolicyLayer and add a rule for create_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 Sora2 MCP. Nothing to install.
create_video 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 create_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 create_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.
create_video is provided by the Sora2 MCP server (nanameru/sora2-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 →