Generate an AI video asynchronously using Sora Version 2 with callback. Similar to sora_generate_video_v2 but returns immediately with a task ID. The result will be POSTed to your callback URL when generation completes. Use this when: - You don't want to wait for the generation ...
Accepts URL/endpoint input (callback_url)
Part of the Mcp Sora MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use sora_generate_video_v2_async to create or modify resources in Mcp Sora. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call sora_generate_video_v2_async repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Sora.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
sora_generate_video_v2_async:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Mcp Sora policy for all 10 tools.
Agents calling write-class tools like sora_generate_video_v2_async have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Generate an AI video asynchronously using Sora Version 2 with callback. Similar to sora_generate_video_v2 but returns immediately with a task ID. The result will be POSTed to your callback URL when generation completes. Use this when: - You don't want to wait for the generation to complete - You have a webhook endpoint to receive results - You're integrating with an async workflow Returns: Task ID that you can use to correlate with the callback. . It is categorised as a Write tool in the Mcp Sora MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for sora_generate_video_v2_async. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sora MCP server.
sora_generate_video_v2_async 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 sora_generate_video_v2_async rule in your Intercept 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 Intercept policy for sora_generate_video_v2_async. 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.
sora_generate_video_v2_async is provided by the Mcp Sora MCP server (acedatacloud-mcp/mcp-sora). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.