create_event_bus

Generate a typed LOCAL pub/sub event bus: a pure STATIC class (NOT a Component — nothing to place in the scene) with Subscribe<T>(owner, Action<T>), Unsubscribe(owner) (removes all of that owner

SERVERSbox SOURCEsbox-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sbox/create-event-bus.md

WHAT IT DOES

What create_event_bus does on Sbox

AI agents use create_event_bus to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.

RISK

Why create_event_bus is rated Medium

Creates a new static class code artifact; reversible, no destructive or financial impact.

From the tool's definition Generate a typed LOCAL pub/sub event bus static class

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_event_bus safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_event_bus, this is the rule to start with:

create_event_bus Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_event_bus": {
      "limits": [
        {
          "counter": "create_event_bus_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every create_event_bus call is checked against it from then on.

FAQ

Questions about create_event_bus

What does the create_event_bus tool do? +

Generate a typed LOCAL pub/sub event bus: a pure STATIC class (NOT a Component — nothing to place in the scene) with Subscribe<T>(owner, Action<T>), Unsubscribe(owner) (removes all of that owner. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_event_bus? +

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

What risk level is create_event_bus? +

create_event_bus is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_event_bus? +

Yes. Add a rate_limit block to the create_event_bus 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 create_event_bus completely? +

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

create_event_bus is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 287 Sbox tools →

Across the catalogue

calendar_create_event on Apple Apps MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →