add_audio_bus_config
Add a new audio bus at a specific position
This record as markdown: /tools/keeveeg-godot-mcp/add-audio-bus-config.md
What add_audio_bus_config does on Godot
AI agents use add_audio_bus_config 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 |
|---|---|---|---|
name | string | Yes | Bus name |
index | integer | — | Position in bus list (omit to append) |
Parameters from the server's own tool schema.
Why add_audio_bus_config is rated Medium
This tool creates a new audio bus configuration, which is a reversible modification to the project's audio setup. It does not execute arbitrary code, delete data, or move money. While it modifies the engine state, the change is undoable (typical in Godot editors via undo/redo).
From the tool's definition Tool name 'add_audio_bus_config' and description 'Add a new audio bus at a specific position' indicate creation of a new configuration object in the Godot engine's audio subsystem.
Attacks that exploit this kind of access
The rule that runs add_audio_bus_config 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 add_audio_bus_config, this is the rule to start with:
add_audio_bus_config 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 add_audio_bus_config call is checked against it from then on.
Questions about add_audio_bus_config
Add a new audio bus at a specific position. 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.
add_audio_bus_config accepts 2 parameters: name, index. Required: name. 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 add_audio_bus_config: 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.
add_audio_bus_config 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 add_audio_bus_config 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 add_audio_bus_config. 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.
add_audio_bus_config 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