Query multiple video generation tasks at once. Efficiently check the status of multiple tasks in a single request. More efficient than calling sora_get_task multiple times. Use this when: - You have multiple pending generations to check - You want to get status of several vi...
Single-target operation
Part of the Mcp Sora MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call sora_get_tasks_batch to retrieve information from Mcp Sora without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though sora_get_tasks_batch only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
sora_get_tasks_batch:
rules:
- action: allowSee the full Mcp Sora policy for all 10 tools.
Agents calling read-class tools like sora_get_tasks_batch have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Query multiple video generation tasks at once. Efficiently check the status of multiple tasks in a single request. More efficient than calling sora_get_task multiple times. Use this when: - You have multiple pending generations to check - You want to get status of several videos at once - You're tracking a batch of generations Returns: Status and video information for all queried tasks. . It is categorised as a Read tool in the Mcp Sora MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for sora_get_tasks_batch. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sora MCP server.
sora_get_tasks_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sora_get_tasks_batch 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_get_tasks_batch. 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_get_tasks_batch 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.