AI agents call get_video_status to retrieve information from Sora2 MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an existing video generation job and returns metadata about it. It has no side effects, does not modify data, does not execute operations, and does not delete or move resources. It is a straightforward read operation that retrieves information about a background job's progress.
From the tool's definition Tool name and description indicate retrieval of status information only: 'Retrieve the current status and progress of a video generation job.' Returns status values (queued, in_progress, completed, failed) without modifying or executing any operations.
Attacks that exploit this kind of access
Retrieve the current status and progress of a video generation job. Status values: queued, in_progress, completed, failed. It is categorised as a Read tool in the Sora2 MCP MCP Server, which means it retrieves data without modifying state.
Register the Sora2 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 Sora2 MCP. 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 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 →