# get_device

A read tool on the Tolpo MCP server.

Agent View of the PolicyLayer registry record for `get_device`. HTML page: https://policylayer.com/tools/tolpo/get-device

## Facts

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

## Why get_device is rated Low

The tool retrieves device information from a homelab asset database with no modification, deletion, or execution capability. It is a standard read operation with minimal security risk unless the database contains sensitive credentials (low blast radius for accidental misuse).

From the tool's own definition: "Tool name is 'get_device' and sibling tools include 'find_device', 'list_devices_by_category', 'list_devices_by_vlan' — all characteristic of query/retrieval operations on an asset database. Server description emphasizes 'Query' a Markdown-based database."

## Use case

AI agents call get_device to retrieve information from Tolpo 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 Tolpo:

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

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