Remove an audio bus by name.
AI agents call remove_audio_bus to permanently remove resources in Godot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'remove' operation on an audio bus is irreversible. Deleting an audio bus could break audio routing in a game project, orphan audio players that depend on it, and require manual restoration. This is a destructive action with significant blast radius in game development workflows, justifying the Destructive category over Write.
From the tool's definition Tool name 'remove_audio_bus' combined with description 'Remove an audio bus by name' indicates deletion of an audio bus configuration, which cannot be undone without restoration from backup.
Attacks that exploit this kind of access
Remove an audio bus by name. It is categorised as a Destructive tool in the Godot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot MCP Server 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 MCP Server. 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 MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →