audio_bus_add

Add a bus to the project's global AudioServer layout, optionally naming it, positioning it (at_position), and setting its send bus. DESTRUCTIVE (project-wide audio state) — gated by confirmation.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/audio-bus-add.md

WHAT IT DOES

What audio_bus_add does on Breakpoint

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

Parameter	Type	Required	Description
`name`	string	—	Name for the new bus
`send`	string	—	Name of the bus this bus sends its output to
`confirm`	boolean	—	Auto-approve this destructive action (skip the confirmation prompt)
`at_position`	number	—	Insert index (default -1 = append at end)

Parameters from the server's own tool schema.

RISK

Why audio_bus_add is rated Medium

This tool adds a new audio bus to the global AudioServer configuration, which is a creation/modification operation. Although it affects project-wide state and the description mentions 'DESTRUCTIVE', the operation is not irreversible: audio buses can be deleted, renamed, or repositioned. It therefore fits Write (creates/modifies data reversibly) rather than Destructive.

From the tool's definition Description states 'Add a bus to the project's global AudioServer layout' with options to name, position, and set send bus. The tool creates or modifies audio infrastructure in the project.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audio_bus_add safely

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

audio_bus_add Rate-limited

audio_bus_add 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": {
    "audio_bus_add": {
      "limits": [
        {
          "counter": "audio_bus_add_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 Breakpoint, apply this rule, and every audio_bus_add call is checked against it from then on.

FAQ

Questions about audio_bus_add

What does the audio_bus_add tool do? +

Add a bus to the project's global AudioServer layout, optionally naming it, positioning it (at_position), and setting its send bus. DESTRUCTIVE (project-wide audio state) — gated by confirmation. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does audio_bus_add accept? +

audio_bus_add accepts 4 parameters: name, send, confirm, at_position. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on audio_bus_add? +

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

What risk level is audio_bus_add? +

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

Can I rate-limit audio_bus_add? +

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

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

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

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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