plan_video
Write a short vertical video with the iDos Games video studio's AI director: an idea becomes a VideoSpec (format, scene, characters, lines with emotions and actions, captions) built from the studio library, plus the plan — for each element whether the library fits or an AI asset should be generat...
This record as markdown: /tools/com-idosgames-platform/plan-video.md
What plan_video does on iDos Games
AI agents use plan_video to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cast | integer | — | How many characters (optional — the format decides). |
idea | string | Yes | What the video is about, in any language (≤ 600 characters). |
mode | string | — | unique (default) — the plan may ask for AI assets; quick — library only, AI items dropped. |
style | string | — | Style family of the studio library, e.g. voxel-warm or chibi-2d (default voxel-warm). |
format | string | Yes | Format id from list_video_formats, e.g. dialogue@1, story@1, top5@1, quiz@1, whatif@1. |
language | string | — | Language of the lines in words, e.g. English or Russian (default English). |
title_id | string | — | Which game this is for — a label for the report, optional (credits are the publisher's). |
generation_id | string | — | Finish a plan whose generation was still running (optional; no new charge). |
Parameters from the server's own tool schema.
Why plan_video is rated Medium
An AI agent can call plan_video faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs plan_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 plan_video, this is the rule to start with:
plan_video stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 plan_video call is checked against it from then on.
Questions about plan_video
Write a short vertical video with the iDos Games video studio's AI director: an idea becomes a VideoSpec (format, scene, characters, lines with emotions and actions, captions) built from the studio library, plus the plan — for each element whether the library fits or an AI asset should be generated (next lists the generate_asset calls: pass them the returned package and the item's slot, and the asset takes its place). Refs outside the library are replaced with the closest library asset (listed in repaired), the cast is fitted to the format. Costs one text generation of the publisher's credits (see estimate_media_cost, modality text). If it is not ready in about two minutes the answer carries the generation id — call plan_video again with generation_id to finish it without paying twice. The answer is a video PACKAGE ({ spec, assets }) and, when title_id names a game with the video studio, a link that opens it in that app's editor — the player watches, edits and exports the MP4 on the device (there is no server render). Formats and assets: list_video_formats, search_assets. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
plan_video accepts 8 parameters: cast, idea, mode, style, format, language, title_id, generation_id. Required: idea, format. 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 plan_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.
plan_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_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 plan_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.
plan_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