10 tools. 6 can modify or destroy data without limits.
6 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (sora_generate_video, sora_generate_video_async, sora_generate_video_from_image) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
sora_generate_video:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
sora_get_task:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Mcp Sora server has 6 write tools including sora_generate_video, sora_generate_video_async, sora_generate_video_from_image. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
10 tools across 2 categories: Read, Write. 4 are read-only. 6 can modify, create, or delete data.
One line change. Instead of running the Mcp Sora server directly, prefix it with Intercept: intercept -c acedatacloud-mcp-mcp-sora.yaml -- npx -y @acedatacloud-mcp/mcp-sora. Download a pre-built policy from policylayer.com/policies/acedatacloud-mcp-mcp-sora and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.