audio_bus_set_volume
Set the volume (in dB) of a named bus on the global AudioServer. DESTRUCTIVE (project-wide audio state) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/audio-bus-set-volume.md
What audio_bus_set_volume does on Breakpoint
AI agents use audio_bus_set_volume 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 | Bus name |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
volume_db | number | Yes | Volume in dB |
Parameters from the server's own tool schema.
Why audio_bus_set_volume is rated Medium
This is a Write operation because it modifies audio bus configuration in a reversible way. Although the description uses the word 'DESTRUCTIVE', that appears to be referring to the scope (project-wide impact) rather than the irreversibility criterion that defines the Destructive category. Audio settings can be undone by setting the volume to a different value.
From the tool's definition The tool description explicitly states it "Set[s] the volume (in dB) of a named bus on the global AudioServer" and modifies "project-wide audio state".
Attacks that exploit this kind of access
The rule that runs audio_bus_set_volume 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_set_volume, this is the rule to start with:
audio_bus_set_volume 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_set_volume call is checked against it from then on.
Questions about audio_bus_set_volume
Set the volume (in dB) of a named bus on the global AudioServer. 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_set_volume accepts 3 parameters: bus, confirm, volume_db. Required: bus, volume_db. 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_set_volume: 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_set_volume 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_set_volume 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_set_volume. 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_set_volume 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