remove_audio_bus
Remove an audio bus by index (cannot remove Master at index 0)
This record as markdown: /tools/keeveeg-godot-mcp/remove-audio-bus.md
What remove_audio_bus does on Godot
AI agents call remove_audio_bus to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | integer | Yes | Bus index to remove (1+, cannot remove Master) |
Parameters from the server's own tool schema.
Why remove_audio_bus is rated Critical
The tool removes an audio bus, which is an irreversible deletion of a configuration element. The parenthetical note about not being able to remove Master implies other buses are permanently deleted, placing this in the Destructive category. Severity is medium as it affects project audio configuration but is limited in blast radius.
From the tool's definition Remove an audio bus by index (cannot remove Master at index 0)
Attacks that exploit this kind of access
The rule that runs remove_audio_bus 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 remove_audio_bus, this is the rule to start with:
remove_audio_bus is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every remove_audio_bus call is checked against it from then on.
Questions about remove_audio_bus
Remove an audio bus by index (cannot remove Master at index 0). It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_audio_bus accepts 1 parameter: index. Required: index. 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 remove_audio_bus: 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.
remove_audio_bus is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_audio_bus 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 remove_audio_bus. 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.
remove_audio_bus 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.
Across the catalogue