set_audio_bus_layout
Replace the entire audio bus layout with the given bus definitions
This record as markdown: /tools/keeveeg-godot-mcp/set-audio-bus-layout.md
What set_audio_bus_layout does on Godot
AI agents use set_audio_bus_layout to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
buses | array | Yes | Ordered list of audio buses (first is always 'Master') |
Parameters from the server's own tool schema.
Why set_audio_bus_layout is rated Medium
This tool writes/modifies audio bus layout configuration in a Godot project. It is reversible (a new layout can be written to replace it), so it falls under Write rather than Destructive. The severity is medium because misuse could corrupt audio setup and require reconfiguration, but it does not permanently delete data or execute arbitrary code.
From the tool's definition Tool description states 'Replace the entire audio bus layout with the given bus definitions' — this modifies the audio configuration by replacing (writing) an entire layout.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_audio_bus_layout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_audio_bus_layout, this is the rule to start with:
set_audio_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 Godot, apply this rule, and every set_audio_bus_layout call is checked against it from then on.
Questions about set_audio_bus_layout
Replace the entire audio bus layout with the given bus definitions. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_audio_bus_layout accepts 1 parameter: buses. Required: buses. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for set_audio_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 Godot. Nothing to install.
set_audio_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 set_audio_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 set_audio_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.
set_audio_bus_layout is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue