set_enabled
Enable or disable a GameObject (disabled objects are invisible and inactive)
This record as markdown: /tools/sbox/set-enabled.md
What set_enabled does on Sbox
AI agents use set_enabled 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 set_enabled is rated Medium
This tool modifies game object state reversibly—disabled objects can be re-enabled. It does not create, delete, or execute code; it changes object properties. While it affects gameplay, the change is not permanent or destructive, qualifying it as Write rather than Execute or Destructive. Severity is medium because disabling critical gameplay objects could break game functionality, but the action is reversible.
From the tool's definition Tool enables or disables GameObjects, which modifies their state (visibility and activity status). Description explicitly states 'Enable or disable' and notes effects on visibility and activity.
Attacks that exploit this kind of access
The rule that runs set_enabled 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 set_enabled, this is the rule to start with:
set_enabled 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 set_enabled call is checked against it from then on.
Questions about set_enabled
Enable or disable a GameObject (disabled objects are invisible and inactive). 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 set_enabled: 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.
set_enabled 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 set_enabled 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 set_enabled. 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.
set_enabled 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