trigger_hotload
Force s&box to recompile and hotload all C# scripts immediately. Use after creating or editing scripts to see changes in real-time
This record as markdown: /tools/sbox/trigger-hotload.md
What trigger_hotload does on Sbox
AI agents invoke trigger_hotload to trigger actions in Sbox. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why trigger_hotload is rated High
This tool runs a recompilation and hotload operation in the s&box game engine—a code execution action that triggers compilation of C# scripts and reloads them into a running process.
From the tool's definition Tool name 'trigger_hotload' and description 'Force s&box to recompile and hotload all C# scripts immediately' indicate execution of a compilation and code reloading process.
Attacks that exploit this kind of access
The rule that runs trigger_hotload 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 trigger_hotload, this is the rule to start with:
trigger_hotload stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 trigger_hotload call is checked against it from then on.
Questions about trigger_hotload
Force s&box to recompile and hotload all C# scripts immediately. Use after creating or editing scripts to see changes in real-time. It is categorised as a Execute tool in the Sbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sbox MCP server in PolicyLayer and add a rule for trigger_hotload: 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.
trigger_hotload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_hotload 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 trigger_hotload. 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.
trigger_hotload 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