generate_world_from_media_asset
AI agents invoke generate_world_from_media_asset to trigger actions in Worldlabs. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on sibling tools like generate_world_from_image and generate_world_from_video, this tool likely triggers an external 3D world generation operation from a media asset, which is an Execute-category action. However, the empty description significantly lowers confidence. Generation operations consume resources and trigger external pipelines, making severity high if misused at scale.
From the tool's definition Tool name 'generate_world_from_media_asset' — no description provided; name implies triggering a generation pipeline from a media asset.
Documented attack patterns abuse exactly the kind of access generate_world_from_media_asset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Worldlabs, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_world_from_media_asset:
{
"version": "1",
"default": "deny",
"tools": {
"generate_world_from_media_asset": {
"limits": [
{
"counter": "generate_world_from_media_asset_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_world_from_media_asset stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
generate_world_from_media_asset. It is categorised as a Execute tool in the Worldlabs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Worldlabs MCP server in PolicyLayer and add a rule for generate_world_from_media_asset: 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 Worldlabs. Nothing to install.
generate_world_from_media_asset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_world_from_media_asset 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 generate_world_from_media_asset. 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.
generate_world_from_media_asset is provided by the Worldlabs MCP server (sandraschi/worldlabs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Worldlabs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Worldlabs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.