create_sound_event
Create a new sound event file (.sound) with volume, pitch, distance falloff, and looping settings
This record as markdown: /tools/sbox/create-sound-event.md
What create_sound_event does on Sbox
AI agents use create_sound_event to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why create_sound_event is rated Medium
This tool creates new assets in the game engine, which is a reversible write operation. While it modifies the game state by adding sound event files, these files can be deleted or edited, making it Write rather than Destructive.
From the tool's definition Tool description states 'Create a new sound event file (.sound)' — this is a create operation that generates new data files with specified properties (volume, pitch, distance falloff, looping settings).
Attacks that exploit this kind of access
The rule that runs create_sound_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_sound_event, this is the rule to start with:
create_sound_event 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 Sbox, apply this rule, and every create_sound_event call is checked against it from then on.
Questions about create_sound_event
Create a new sound event file (.sound) with volume, pitch, distance falloff, and looping settings. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for create_sound_event: 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 Sbox. Nothing to install.
create_sound_event 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 create_sound_event 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 create_sound_event. 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.
create_sound_event is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue