High Risk →

broadcast_custom_event

Broadcasts a custom event to all WebSocket clients. Args: event_data: Data to send with the event

How to control broadcast_custom_event ↓

AI agents invoke broadcast_custom_event to trigger actions in OBS MCP Server. 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.

High Risk

This tool triggers an external operation by broadcasting data to all connected WebSocket clients. It doesn't merely read or write stored data — it actively pushes an event to connected clients, which could trigger downstream actions in those clients. The blast radius is medium since misuse could disrupt connected clients or trigger unintended behaviors in any listeners.

From the tool's definition Broadcasts a custom event to all WebSocket clients

Documented attack patterns abuse exactly the kind of access broadcast_custom_event gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and OBS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for broadcast_custom_event:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "broadcast_custom_event": {
      "limits": [
        {
          "counter": "broadcast_custom_event_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

broadcast_custom_event 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.

  1. Create a free account and register OBS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the broadcast_custom_event tool do? +

Broadcasts a custom event to all WebSocket clients. Args: event_data: Data to send with the event. It is categorised as a Execute tool in the OBS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on broadcast_custom_event? +

Register the OBS MCP Server MCP server in PolicyLayer and add a rule for broadcast_custom_event: 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 OBS MCP Server. Nothing to install.

What risk level is broadcast_custom_event? +

broadcast_custom_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit broadcast_custom_event? +

Yes. Add a rate_limit block to the broadcast_custom_event 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.

How do I block broadcast_custom_event completely? +

Set action: deny in the PolicyLayer policy for broadcast_custom_event. 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.

What MCP server provides broadcast_custom_event? +

broadcast_custom_event is provided by the OBS MCP Server MCP server (royshil/obs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OBS MCP Server tool call.

Deterministic rules across all 200 OBS MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

200 OBS MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.