# create_weighted_loot_table

Generate a cumulative-weight random loot picker: parallel Name/Weight lists (inspector-editable), a Roll() method that returns a winning entry name and fires a static OnLoot event, and optional pity (guarantee the last/rarest entry after PityAfter consecutive non-rare rolls). Roll() is host-authoritative -- only call it on the host and replicate the result (clients rolling their own loot is equivalent to clients writing their own money balance). Optionally attached to an existing GameObject by GUID (after a hotload).

Agent View of the PolicyLayer registry record for `create_weighted_loot_table`. HTML page: https://policylayer.com/tools/sbox/create-weighted-loot-table

## Facts

- Tool: `create_weighted_loot_table`
- 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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why create_weighted_loot_table is rated Medium

This tool generates and writes code/components for a weighted loot table system into the game engine. It creates a new component with properties and methods, which is a Write operation (creating/modifying game assets or code). While it mentions 'Roll() is host-authoritative' analogous to writing a money balance, the tool itself is generating the loot table structure, not executing financial transactions.

From the tool's own definition: "Generate a cumulative-weight random loot picker... parallel Name/Weight lists (inspector-editable), a Roll() method that returns a winning entry name and fires a static OnLoot event"

## Use case

AI agents use create_weighted_loot_table 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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_weighted_loot_table": {
      "limits": [
        {
          "counter": "create_weighted_loot_table_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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