add_audio_bus · Godot MCP: Risk & Policy

WHAT IT DOES

What add_audio_bus does on Godot

AI agents use add_audio_bus 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.

PARAMETERS

Parameter	Type	Required	Description
`send_to`	object	—	Send target bus
`bus_name`	string	Yes	New bus name
`volume_db`	object	—	Volume in dB
`layout_path`	object	—	Path to AudioBusLayout .tres

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why add_audio_bus needs a policy

This tool creates a new audio bus, which is a reversible modification to the project's audio configuration. It does not execute arbitrary code, delete data irreversibly, or cause financial impact. The 'add' operation is characteristic of Write category tools.

From the tool's definition Tool name 'add_audio_bus' with description 'Add audio bus to layout' indicates creation of a new audio bus configuration in the Godot Engine project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_audio_bus Rate-limited

add_audio_bus 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_audio_bus": {
      "limits": [
        {
          "counter": "add_audio_bus_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about add_audio_bus

What does the add_audio_bus tool do? +

Add audio bus to layout. 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.

What parameters does add_audio_bus accept? +

add_audio_bus accepts 4 parameters: send_to, bus_name, volume_db, layout_path. Required: bus_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_audio_bus? +

Register the Godot MCP server in PolicyLayer and add a rule for add_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.

What risk level is add_audio_bus? +

add_audio_bus is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_audio_bus? +

Yes. Add a rate_limit block to the add_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.

How do I block add_audio_bus completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_audio_bus? +

add_audio_bus is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.