audio_set_bus_layout
Save the current AudioServer bus layout (buses, effects, volumes) to a .tres resource on disk (default res://default_bus_layout.tres) via generate_bus_layout + ResourceSaver.save. DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/audio-set-bus-layout.md
What audio_set_bus_layout does on Breakpoint
AI agents use audio_set_bus_layout 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 |
|---|---|---|---|
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | — | Destination res:// path (default res://default_bus_layout.tres) |
Parameters from the server's own tool schema.
Why audio_set_bus_layout is rated Medium
This tool writes/overwrites a file on disk (a .tres resource). While the description labels it 'DESTRUCTIVE', it writes/saves data rather than deleting or irreversibly destroying it — the file can be restored or overwritten again. The most accurate category is Write (creates or modifies data on disk).
From the tool's definition Save the current AudioServer bus layout (buses, effects, volumes) to a .tres resource on disk via generate_bus_layout + ResourceSaver.save. DESTRUCTIVE (writes a file) — gated by confirmation.
Attacks that exploit this kind of access
The rule that runs audio_set_bus_layout 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_set_bus_layout, this is the rule to start with:
audio_set_bus_layout 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_set_bus_layout call is checked against it from then on.
Questions about audio_set_bus_layout
Save the current AudioServer bus layout (buses, effects, volumes) to a .tres resource on disk (default res://default_bus_layout.tres) via generate_bus_layout + ResourceSaver.save. DESTRUCTIVE (writes a file) — 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_set_bus_layout accepts 2 parameters: confirm, to_path. 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_set_bus_layout: 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_set_bus_layout 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_set_bus_layout 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_set_bus_layout. 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_set_bus_layout 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