Check the status of a video generation operation. If the video is still processing, returns the current status. If the video is complete, returns the video data. Parameters: - operationId: The operation ID from gemini-video-generate (optional - uses last operation if not provided) - outputPath: O...
AI agents call gemini-video-check to retrieve information from Gemini MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a status-checking and data-retrieval tool. It queries the state of an existing video generation operation and optionally retrieves completed video data. It has no side effects, cannot modify or delete data, and does not execute new operations or commands. The outputPath parameter is merely for directing already-generated data to a file destination, which is still a read operation.
From the tool's definition Tool description states it 'Check the status of a video generation operation' and 'returns the current status' or 'returns the video data.' The parameters are operationId (lookup reference) and outputPath (optional destination).
Attacks that exploit this kind of access
Check the status of a video generation operation. If the video is still processing, returns the current status. If the video is complete, returns the video data. Parameters: - operationId: The operation ID from gemini-video-generate (optional - uses last operation if not provided) - outputPath: Optional path to save the video file when complete. It is categorised as a Read tool in the Gemini MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for gemini-video-check: 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 Gemini MCP Server. Nothing to install.
gemini-video-check 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 gemini-video-check 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 gemini-video-check. 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.
gemini-video-check is provided by the Gemini MCP Server MCP server (riotofgeese/gemini-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 →