This record as markdown: /tools/sbox/set-fog.md
What set_fog does on Sbox
AI agents use set_fog 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_fog is rated Medium
This tool modifies the game scene by adding or updating fog properties, which is a creative/design operation. It does not execute arbitrary code, delete data irreversibly, or cause external side effects beyond the game environment. The reversibility and non-destructive nature places it in Write rather than Execute or Destructive.
From the tool's definition set_fog adds or updates fog in the active scene, modifying scene state with an operation that is reversible (fog can be removed or changed to different parameters).
Attacks that exploit this kind of access
The rule that runs set_fog 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_fog, this is the rule to start with:
set_fog 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_fog call is checked against it from then on.
Questions about set_fog
Add or update fog in the active scene. Types:. 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_fog: 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_fog 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_fog 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_fog. 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_fog 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