Add an AudioStreamPlayer node to the scene.
AI agents use add_audio_player to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
The tool creates a new scene node (AudioStreamPlayer), which is a write operation that modifies the scene structure. It is reversible (the node can be deleted), so it does not rise to Destructive. The severity is medium because misuse could clutter or corrupt a scene, but the effect is contained to node creation and easily undone.
From the tool's definition Tool description states 'Add an AudioStreamPlayer node to the scene' — this creates a new node in the Godot scene tree, a reversible modification of the project state.
Attacks that exploit this kind of access
Add an AudioStreamPlayer node to the scene. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server 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 MCP Server. 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 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 →