prepare_media_upload
AI agents use prepare_media_upload to create or update resources in Worldlabs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Worldlabs environment.
The tool creates or modifies state by preparing media for upload, which is reversible and characteristic of Write operations. Given the context (World Labs media generation pipeline), this likely prepares files for ingestion into the world generation process. Severity is medium because misuse could waste resources or consume quota, but cannot directly delete data or execute arbitrary code.
From the tool's definition Tool name 'prepare_media_upload' indicates creation or modification of media assets. No description provided, but the verb 'prepare' combined with 'upload' suggests staging data for transmission, a write operation.
Documented attack patterns abuse exactly the kind of access prepare_media_upload 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 prepare_media_upload:
{
"version": "1",
"default": "deny",
"tools": {
"prepare_media_upload": {
"limits": [
{
"counter": "prepare_media_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}prepare_media_upload 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.
Free to start. No card required.
prepare_media_upload. It is categorised as a Write tool in the Worldlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Worldlabs MCP server in PolicyLayer and add a rule for prepare_media_upload: 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.
prepare_media_upload 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 prepare_media_upload 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 prepare_media_upload. 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.
prepare_media_upload 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.