Broadcast spatial audio (Music/Ambience) to the scene.
AI agents invoke broadcast_spatial_audio 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.
Broadcasting audio to a scene is an external operation that triggers an effect in the 3D world environment. It doesn't merely read data or write a reversible record — it actively pushes audio output to an active scene, making it an Execute-category action. Misuse could disrupt active sessions but has limited blast radius.
From the tool's definition Broadcast spatial audio (Music/Ambience) to the scene
Documented attack patterns abuse exactly the kind of access broadcast_spatial_audio 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 broadcast_spatial_audio:
{
"version": "1",
"default": "deny",
"tools": {
"broadcast_spatial_audio": {
"limits": [
{
"counter": "broadcast_spatial_audio_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}broadcast_spatial_audio 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.
Broadcast spatial audio (Music/Ambience) to the scene. 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 broadcast_spatial_audio: 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.
broadcast_spatial_audio 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 broadcast_spatial_audio 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 broadcast_spatial_audio. 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.
broadcast_spatial_audio 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.