Get the status and details of a video generation job. Returns information about whether the video is still processing, completed, or failed.
AI agents call get_video_status to retrieve information from Sora 2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns metadata about an existing video generation job's state. It performs no modifications, deletions, executions, or financial transactions. It is a straightforward Read operation analogous to a status check or fetch query.
From the tool's definition The tool name is 'get_video_status' and the description states it 'Get[s] the status and details of a video generation job.
Attacks that exploit this kind of access
Get the status and details of a video generation job. Returns information about whether the video is still processing, completed, or failed. It is categorised as a Read tool in the Sora 2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sora 2 MCP Server MCP server in PolicyLayer and add a rule for get_video_status: 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 Sora 2 MCP Server. Nothing to install.
get_video_status 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 get_video_status 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 get_video_status. 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.
get_video_status is provided by the Sora 2 MCP Server MCP server (writingmate/sora-2-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 →