build_terrain_mesh
Build a standalone heightmap terrain mesh from a hills/clearings JSON spec — independent of MapBuilder. Use when you don
This record as markdown: /tools/sbox/build-terrain-mesh.md
What build_terrain_mesh does on Sbox
AI agents invoke build_terrain_mesh 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 build_terrain_mesh is rated High
This tool triggers a generative operation within the s&box game engine, building a terrain mesh from a specification. It's not merely reading data, nor is it a simple write/update to existing data — it executes a mesh-building process that produces engine-level artifacts.
From the tool's definition 'Build a standalone heightmap terrain mesh from a hills/clearings JSON spec' — actively constructs/generates geometry in the game engine environment
Attacks that exploit this kind of access
The rule that runs build_terrain_mesh 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 build_terrain_mesh, this is the rule to start with:
build_terrain_mesh 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 build_terrain_mesh call is checked against it from then on.
Questions about build_terrain_mesh
Build a standalone heightmap terrain mesh from a hills/clearings JSON spec — independent of MapBuilder. Use when you don. 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 build_terrain_mesh: 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.
build_terrain_mesh 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 build_terrain_mesh 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 build_terrain_mesh. 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.
build_terrain_mesh 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