audio_bus_add_effect
Instantiate an AudioEffect subclass (by class name, e.g. "AudioEffectReverb") and add it to a named bus on the global AudioServer, optionally at a position in the bus's effect chain. DESTRUCTIVE (project-wide audio state) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/audio-bus-add-effect.md
What audio_bus_add_effect does on Breakpoint
AI agents use audio_bus_add_effect 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 |
|---|---|---|---|
bus | string | Yes | Target bus name |
effect | string | Yes | AudioEffect subclass name, e.g. "AudioEffectReverb", "AudioEffectDelay" |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
at_position | number | — | Insert index within the bus's effect chain (default -1 = append) |
Parameters from the server's own tool schema.
Why audio_bus_add_effect is rated Medium
This tool adds/creates a new audio effect to an audio bus, which is a write/modify operation on project-wide audio state. While the description labels it 'DESTRUCTIVE', it is actually adding (not irreversibly deleting or overwriting) an effect — it modifies state but appears reversible (effects can be removed). The 'gated by confirmation' note suggests caution but doesn't change the fundamental category.
From the tool's definition Instantiate an AudioEffect subclass and add it to a named bus on the global AudioServer, optionally at a position in the bus's effect chain
Attacks that exploit this kind of access
The rule that runs audio_bus_add_effect 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_effect, this is the rule to start with:
audio_bus_add_effect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every audio_bus_add_effect call is checked against it from then on.
Questions about audio_bus_add_effect
Instantiate an AudioEffect subclass (by class name, e.g. "AudioEffectReverb") and add it to a named bus on the global AudioServer, optionally at a position in the bus's effect chain. 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.
audio_bus_add_effect accepts 4 parameters: bus, effect, confirm, at_position. Required: bus, effect. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for audio_bus_add_effect: 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.
audio_bus_add_effect 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 audio_bus_add_effect 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 audio_bus_add_effect. 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.
audio_bus_add_effect 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.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue