Create and configure an AudioStreamPlayer node (2D or 3D)
AI agents use setup_audio_player to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.
This tool creates and modifies scene data (a new AudioStreamPlayer node) in a reversible manner. It does not execute arbitrary code, delete data, move money, or trigger irreversible operations. The scope is limited to setting up an audio player component in the game engine, which is a standard Write operation on game asset configuration.
From the tool's definition Tool description states 'Create and configure an AudioStreamPlayer node' - the verbs 'create' and 'configure' indicate data modification operations. This is creating a new node in the Godot scene tree and setting its properties.
Attacks that exploit this kind of access
Create and configure an AudioStreamPlayer node (2D or 3D). It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for setup_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 Unified. Nothing to install.
setup_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 setup_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 setup_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.
setup_audio_player is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). 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 →