This record as markdown: /tools/yanhuifair-godot-mcp/add-bus-effect.md
What add_bus_effect does on Godot
AI agents use add_bus_effect 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 |
|---|---|---|---|
bus_index | number | Yes | Bus index |
effect_type | string | Yes | Effect type |
layout_path | object | — | |
effect_params | object | — | Effect parameters |
Parameters from the server's own tool schema.
Why add_bus_effect is rated Medium
This tool creates or modifies audio bus effects, which is a reversible change to project state. It does not execute arbitrary code, delete data, or move money. While it affects runtime audio behavior, the modification is non-destructive and can be undone. Categorized as Write rather than Execute because it operates at the configuration level rather than triggering dynamic code execution or external operations.
From the tool's definition Tool name 'add_bus_effect' and description 'Add effect to audio bus' indicate creation/modification of audio configuration within a Godot project.
Attacks that exploit this kind of access
The rule that runs add_bus_effect 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_bus_effect, this is the rule to start with:
add_bus_effect 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_bus_effect call is checked against it from then on.
Questions about add_bus_effect
Add effect to audio bus. 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_bus_effect accepts 4 parameters: bus_index, effect_type, layout_path, effect_params. Required: bus_index, effect_type. 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_bus_effect: 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_bus_effect 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_bus_effect 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_bus_effect. 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_bus_effect 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue