audio_player_create

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/audio-player-create.md

WHAT IT DOES

What audio_player_create does on Breakpoint

AI agents use audio_player_create to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.

Parameter	Type	Required	Description
`bus`	string	—	Target audio bus name (default "Master")
`dim`	string	—	Player kind: "none" (default, AudioStreamPlayer), "2d" (AudioStreamPlayer2D), or "3d" (AudioStreamPlayer3D)
`name`	string	—	Node name (default matches the player class)
`autoplay`	boolean	—	Whether the player starts automatically on scene load
`volume_db`	number	—	Player volume in dB
`parent_path`	string	Yes	Parent node path relative to the scene root; "." for the root
`stream_path`	string	—	res:// path to an AudioStream to assign to the new player

Parameters from the server's own tool schema.

RISK

Why audio_player_create is rated Medium

This tool creates (instantiates) a new node/object in a scene with configurable properties. This is a write operation that modifies the scene state reversibly via undo. While it affects scene structure, it does not execute arbitrary code, trigger external operations with unpredictable effects, or destroy data irreversibly. The 'undoable' property confirms reversibility, distinguishing it from destructive actions.

From the tool's definition Tool creates a new AudioStreamPlayer node in a scene with properties like stream_path, autoplay, volume_db, and bus. Description explicitly states 'Add an AudioStreamPlayer...node' and 'undoable', indicating reversible scene modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audio_player_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audio_player_create, this is the rule to start with:

audio_player_create Rate-limited

audio_player_create 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": {
    "audio_player_create": {
      "limits": [
        {
          "counter": "audio_player_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every audio_player_create call is checked against it from then on.

FAQ

Questions about audio_player_create

What does the audio_player_create tool do? +

Add an AudioStreamPlayer / AudioStreamPlayer2D / AudioStreamPlayer3D node under a parent in the edited scene (undoable). dim selects "none" (default, non-positional AudioStreamPlayer), "2d", or "3d". Optional initial stream_path (res:// AudioStream), autoplay, volume_db, bus. In-scene and undoable — not gated. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does audio_player_create accept? +

audio_player_create accepts 7 parameters: bus, dim, name, autoplay, volume_db, parent_path, stream_path. Required: parent_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on audio_player_create? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for audio_player_create: 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 Breakpoint. Nothing to install.

What risk level is audio_player_create? +

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

Can I rate-limit audio_player_create? +

Yes. Add a rate_limit block to the audio_player_create 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 audio_player_create completely? +

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

audio_player_create is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →