# set_light

A write tool on the Tolpo MCP server.

Agent View of the PolicyLayer registry record for `set_light`. HTML page: https://policylayer.com/tools/tolpo/set-light

## Facts

- Tool: `set_light`
- Server: Tolpo (`signerless/tolpo`) — https://policylayer.com/tools/tolpo.md
- Homepage: https://github.com/signerless/tolpo
- 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": "set_light",
    "arguments": {}
  }
}
```

## Why set_light is rated Medium

The tool modifies lighting device state (on/off, brightness, color, etc.), which is reversible and non-destructive. This constitutes Write rather than Execute because it targets a specific resource state change rather than running arbitrary code. Severity is medium: misuse could disrupt occupant comfort or smart home routines, but has no financial, destructive, or safety-critical consequences in typical scenarios.

From the tool's own definition: "Tool name 'set_light' combined with sibling tools 'set_group' and context of 'control of Philips Hue lighting devices' indicates modification of light state. Description is empty, requiring inference from name and server context."

## Use case

AI agents use set_light to create or update resources in Tolpo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tolpo environment.

## Recommended policy (PolicyLayer)

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

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

## Other tools on Tolpo (242)

- `automation_delete` — Destructive — https://policylayer.com/tools/tolpo/automation-delete.md
- `camera_ptz_delete_presets` — Destructive — https://policylayer.com/tools/tolpo/camera-ptz-delete-presets.md
- `camera_storage_format` — Destructive — https://policylayer.com/tools/tolpo/camera-storage-format.md
- `camera_system_reset` — Destructive — https://policylayer.com/tools/tolpo/camera-system-reset.md
- `group_delete` — Destructive — https://policylayer.com/tools/tolpo/group-delete.md
- `light_delete_rule` — Destructive — https://policylayer.com/tools/tolpo/light-delete-rule.md
- `pair_remove` — Destructive — https://policylayer.com/tools/tolpo/pair-remove.md
- `plug_auto_off_cancel` — Destructive — https://policylayer.com/tools/tolpo/plug-auto-off-cancel.md
- `plug_energy_clear` — Destructive — https://policylayer.com/tools/tolpo/plug-energy-clear.md
- `plug_rule_delete` — Destructive — https://policylayer.com/tools/tolpo/plug-rule-delete.md
- `reset_factory` — Destructive — https://policylayer.com/tools/tolpo/reset-factory.md
- `reset_reboot` — Destructive — https://policylayer.com/tools/tolpo/reset-reboot.md
- `room_delete` — Destructive — https://policylayer.com/tools/tolpo/room-delete.md
- `vacuum_remove_schedule` — Destructive — https://policylayer.com/tools/tolpo/vacuum-remove-schedule.md
- `vacuum_reset_consumable` — Destructive — https://policylayer.com/tools/tolpo/vacuum-reset-consumable.md
- `vacuum_return_home` — Destructive — https://policylayer.com/tools/tolpo/vacuum-return-home.md
- `automation_dry_run` — Execute — https://policylayer.com/tools/tolpo/automation-dry-run.md
- `automation_tick` — Execute — https://policylayer.com/tools/tolpo/automation-tick.md
- `camera_ptz_patrol` — Execute — https://policylayer.com/tools/tolpo/camera-ptz-patrol.md
- `camera_ptz_stop` — Execute — https://policylayer.com/tools/tolpo/camera-ptz-stop.md
- `camera_recordings_day` — Execute — https://policylayer.com/tools/tolpo/camera-recordings-day.md
- `camera_system_reboot` — Execute — https://policylayer.com/tools/tolpo/camera-system-reboot.md
- `network_new_destinations` — Execute — https://policylayer.com/tools/tolpo/network-new-destinations.md
- `vacuum_clean_rooms` — Execute — https://policylayer.com/tools/tolpo/vacuum-clean-rooms.md
- `vacuum_empty_bin` — Execute — https://policylayer.com/tools/tolpo/vacuum-empty-bin.md
- `vacuum_preset` — Execute — https://policylayer.com/tools/tolpo/vacuum-preset.md
- `vacuum_spot` — Execute — https://policylayer.com/tools/tolpo/vacuum-spot.md
- `vacuum_start` — Execute — https://policylayer.com/tools/tolpo/vacuum-start.md
- `vacuum_stop` — Execute — https://policylayer.com/tools/tolpo/vacuum-stop.md
- `vacuum_task_group` — Execute — https://policylayer.com/tools/tolpo/vacuum-task-group.md
- …and 212 more: https://policylayer.com/tools/tolpo.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=tolpo · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/tolpo