Check status of a queued video job. Status enum: PROCESSING, COMPLETED. POST endpoint with body {model, queue_id}.${X402_OK}
AI agents call venice_video_status to retrieve information from Venice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current state of an existing video processing job. It queries job status without modifying, deleting, or executing any operations. The POST method is used for status retrieval (common in APIs), but the operation itself is idempotent and informational. No data is created, modified, or destroyed. Blast radius is minimal—misuse would only return job status information.
From the tool's definition Tool description states 'Check status of a queued video job' with status enum responses (PROCESSING, COMPLETED). The verb 'check' and 'status' indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access venice_video_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Venice MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for venice_video_status:
{
"version": "1",
"default": "deny",
"tools": {
"venice_video_status": {}
}
}venice_video_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check status of a queued video job. Status enum: PROCESSING, COMPLETED. POST endpoint with body {model, queue_id}.${X402_OK}. It is categorised as a Read tool in the Venice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Venice MCP Server MCP server in PolicyLayer and add a rule for venice_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 Venice MCP Server. Nothing to install.
venice_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 venice_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 venice_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.
venice_video_status is provided by the Venice MCP Server MCP server (veniceai/venice-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Venice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
27 Venice MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.