add_beam
Create an energy/laser beam (BeamEffect) from a position to a target point — additive, tintable. Good for lasers, tracers, magic beams.
This record as markdown: /tools/sbox/add-beam.md
What add_beam does on Sbox
AI agents use add_beam 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 add_beam is rated Medium
This tool creates a new visual effect (BeamEffect) in the game world, modifying the game state by adding a reversible game object. It is a Write operation (creates data) rather than Destructive (deletion is not mentioned and creation of visual effects can be undone in game development contexts).
From the tool's definition Tool name 'add_beam' and description 'Create an energy/laser beam (BeamEffect) from a position to a target point' indicates creation of a visual game object/effect.
Attacks that exploit this kind of access
The rule that runs add_beam 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 add_beam, this is the rule to start with:
add_beam 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 add_beam call is checked against it from then on.
Questions about add_beam
Create an energy/laser beam (BeamEffect) from a position to a target point — additive, tintable. Good for lasers, tracers, magic beams. 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 add_beam: 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.
add_beam 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_beam 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_beam. 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_beam 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