search_assets
Search the video studio's library of characters, scenes, props and music (ready assets every studio has): each entry is a ref to put into a VideoSpec (lib:office-guy@1), its kind (actor | set | prop | music), style family, title, tags, what it can do and its tier (base — free for everyone, premiu...
This record as markdown: /tools/com-idosgames-platform/search-assets.md
What search_assets does on iDos Games
AI agents call search_assets 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 |
|---|---|---|---|
kind | string | — | actor | set | prop | music. |
query | string | — | Words to match in title, tags and what it can do (tags are in en and ru). Empty — all. |
style | string | — | Style family, e.g. voxel-warm or chibi-2d. |
Parameters from the server's own tool schema.
Why search_assets is rated Low
Even though search_assets 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_assets 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 search_assets, this is the rule to start with:
search_assets 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 search_assets call is checked against it from then on.
Questions about search_assets
Search the video studio's library of characters, scenes, props and music (ready assets every studio has): each entry is a ref to put into a VideoSpec (lib:office-guy@1), its kind (actor | set | prop | music), style family, title, tags, what it can do and its tier (base — free for everyone, premium — opened by a pack). Every word of the query must match; filter by kind and style. Read-only; takes no title_id. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
search_assets accepts 3 parameters: kind, query, style. 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 search_assets: 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.
search_assets 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 search_assets 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 search_assets. 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.
search_assets 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