get_video
Poll a video job by id. While it runs the status says so; when it is done the CDN URL is in Assets.
This record as markdown: /tools/com-idosgames-platform/get-video.md
What get_video does on iDos Games
AI agents call get_video to retrieve information from iDos Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
variant | string | — | Variant to fetch, e.g. 720p (optional). |
title_id | string | — | Which game this is for — a label for the report, optional. Credits are always the publisher's, so leaving it out is normal for assets that belong to no game. |
video_id | string | Yes | Job id returned by generate_video. |
content_type | string | — | Desired content type, e.g. video/mp4 (optional). |
Parameters from the server's own tool schema.
Why get_video is rated Low
Even though get_video only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_video, this is the rule to start with:
get_video is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every get_video call is checked against it from then on.
Questions about get_video
Poll a video job by id. While it runs the status says so; when it is done the CDN URL is in Assets. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
get_video accepts 4 parameters: variant, title_id, video_id, content_type. Required: video_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for get_video: 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 iDos Games. Nothing to install.
get_video 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 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. 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 is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue