add_audio_player
Add an AudioStreamPlayer, AudioStreamPlayer2D, or AudioStreamPlayer3D node
This record as markdown: /tools/keeveeg-godot-mcp/add-audio-player.md
What add_audio_player does on Godot
AI agents use add_audio_player 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 | — | Custom node name |
parent | string | Yes | Parent node — '' for scene root |
properties | object | — | Additional player properties (volume_db, autoplay, bus, etc.) |
player_type | string | — | Audio player type |
stream_path | string | — | Audio stream resource path (e.g. 'res://sounds/music.ogg') |
Parameters from the server's own tool schema.
Why add_audio_player is rated Medium
This tool creates (adds) new audio player nodes to a Godot project. Node creation is a reversible modification operation — nodes can be deleted or undone. This is a Write operation (create), not Execute, because it doesn't run arbitrary code or scripts; it merely instantiates a predefined node type.
From the tool's definition Tool is named 'add_audio_player' and described as 'Add an AudioStreamPlayer, AudioStreamPlayer2D, or AudioStreamPlayer3D node' — these operations create new nodes in a Godot scene, which modifies the scene structure reversibly.
Attacks that exploit this kind of access
The rule that runs add_audio_player 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_player, this is the rule to start with:
add_audio_player 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_player call is checked against it from then on.
Questions about add_audio_player
Add an AudioStreamPlayer, AudioStreamPlayer2D, or AudioStreamPlayer3D node. 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_player accepts 5 parameters: name, parent, properties, player_type, stream_path. Required: parent. 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_player: 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_player 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_player 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_player. 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_player 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