broadcast_spatial_notification
AI agents use broadcast_spatial_notification 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.
Broadcasting a notification is a Write operation—it creates/sends data that affects the state of the spatial environment or connected agents. It's reversible (notifications can be cleared/replaced) and has limited blast radius compared to deletion. Severity is medium because spurious notifications could disrupt a voice agent's operation in the scene, but wouldn't cause permanent data loss or financial harm.
From the tool's definition Tool name 'broadcast_spatial_notification' indicates sending/broadcasting messages in a spatial context. Sibling tools show this server manages 3D world generation and state (generate_world_*, delete_world, get_world, list_worlds), suggesting broadcast…
Documented attack patterns abuse exactly the kind of access broadcast_spatial_notification 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_notification:
{
"version": "1",
"default": "deny",
"tools": {
"broadcast_spatial_notification": {
"limits": [
{
"counter": "broadcast_spatial_notification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}broadcast_spatial_notification 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.
broadcast_spatial_notification. 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 broadcast_spatial_notification: 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_notification 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 broadcast_spatial_notification 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_notification. 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_notification 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.