# scene_validate

Validate the active scene for the silent setup footguns that break controllers/physics/cameras: no CameraComponent, no player controller, multiple root Rigidbodies, a Rigidbody with MotionEnabled=false fighting a kinematic root, IsTrigger colliders that Scene.Trace will ignore, child Rigidbodies breaking collider binding, and missing required child anchors. Returns each issue with the GameObject and the exact fix.

Agent View of the PolicyLayer registry record for `scene_validate`. HTML page: https://policylayer.com/tools/sbox/scene-validate

## Facts

- Tool: `scene_validate`
- Server: Sbox (`sbox-mcp-server`) — https://policylayer.com/tools/sbox.md
- Install: `npx -y sbox-mcp-server`
- Homepage: git+https://github.com/LouSputthole/Sbox-Claude.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "scene_validate",
    "arguments": {}
  }
}
```

## Why scene_validate is rated Low

scene_validate is a diagnostic/inspection tool that queries the scene state and reports configuration issues. It has no side effects on the game world, assets, or physics simulation. While it helps debug 'footguns that break' systems, the tool itself only reads and validates; it does not execute fixes or alter the scene. This is categorized as Read despite the domain-specific nature of the validation logic.

From the tool's own definition: "Tool description states it 'Validate[s] the active scene' and 'Returns each issue' — it performs inspection and validation without modifying game state."

Risk signals: Admin/system-level operation

## Use case

AI agents call scene_validate to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Sbox:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scene_validate": {}
  }
}
```

## Other tools on Sbox (206)

- `clear_cave_path` — Destructive — https://policylayer.com/tools/sbox/clear-cave-path.md
- `clear_forest_pois` — Destructive — https://policylayer.com/tools/sbox/clear-forest-pois.md
- `clear_terrain_features` — Destructive — https://policylayer.com/tools/sbox/clear-terrain-features.md
- `debug_clear` — Destructive — https://policylayer.com/tools/sbox/debug-clear.md
- `delete_gameobject` — Destructive — https://policylayer.com/tools/sbox/delete-gameobject.md
- `delete_script` — Destructive — https://policylayer.com/tools/sbox/delete-script.md
- `remove_component` — Destructive — https://policylayer.com/tools/sbox/remove-component.md
- `snap_to_ground` — Destructive — https://policylayer.com/tools/sbox/snap-to-ground.md
- `bake_navmesh` — Execute — https://policylayer.com/tools/sbox/bake-navmesh.md
- `bake_reflections` — Execute — https://policylayer.com/tools/sbox/bake-reflections.md
- `build_terrain_mesh` — Execute — https://policylayer.com/tools/sbox/build-terrain-mesh.md
- `console_run` — Execute — https://policylayer.com/tools/sbox/console-run.md
- `create_event_director` — Execute — https://policylayer.com/tools/sbox/create-event-director.md
- `create_npc_spawner` — Execute — https://policylayer.com/tools/sbox/create-npc-spawner.md
- `create_trigger_zone` — Execute — https://policylayer.com/tools/sbox/create-trigger-zone.md
- `debug_draw_box` — Execute — https://policylayer.com/tools/sbox/debug-draw-box.md
- `debug_draw_ray` — Execute — https://policylayer.com/tools/sbox/debug-draw-ray.md
- `debug_draw_sphere` — Execute — https://policylayer.com/tools/sbox/debug-draw-sphere.md
- `drive_player` — Execute — https://policylayer.com/tools/sbox/drive-player.md
- `execute_csharp` — Execute — https://policylayer.com/tools/sbox/execute-csharp.md
- `focus_object` — Execute — https://policylayer.com/tools/sbox/focus-object.md
- `frame_camera` — Execute — https://policylayer.com/tools/sbox/frame-camera.md
- `invoke_button` — Execute — https://policylayer.com/tools/sbox/invoke-button.md
- `invoke_method` — Execute — https://policylayer.com/tools/sbox/invoke-method.md
- `load_scene` — Execute — https://policylayer.com/tools/sbox/load-scene.md
- `network_spawn` — Execute — https://policylayer.com/tools/sbox/network-spawn.md
- `play_animation` — Execute — https://policylayer.com/tools/sbox/play-animation.md
- `play_sound_preview` — Execute — https://policylayer.com/tools/sbox/play-sound-preview.md
- `playtest` — Execute — https://policylayer.com/tools/sbox/playtest.md
- `recompile_asset` — Execute — https://policylayer.com/tools/sbox/recompile-asset.md
- …and 176 more: https://policylayer.com/tools/sbox.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=sbox · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/sbox