device.registry.list
List every physical device reachable through the calling agent's own linked vendor accounts (Tuya first). Returns each device's vendor id, name, category, and online status, grouped by connection_id. Empty if the agent has not linked any vendor account yet -- see /connect/device/vendors.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/device.registry.list.md
What device.registry.list does on Apibase
AI agents call device.registry.list to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
vendor | string | — | Filter to one linked vendor's devices, e.g. 'tuya' (omit to list all) |
Parameters from the server's own tool schema.
Why device.registry.list is rated Low
Retrieves device inventory and status without modification; medium severity due to IoT reconnaissance exposure.
From the tool's definition List every physical device reachable through the calling agent's own linked vendor accounts
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs device.registry.list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device.registry.list, this is the rule to start with:
device.registry.list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every device.registry.list call is checked against it from then on.
Questions about device.registry.list
List every physical device reachable through the calling agent's own linked vendor accounts (Tuya first). Returns each device's vendor id, name, category, and online status, grouped by connection_id. Empty if the agent has not linked any vendor account yet -- see /connect/device/vendors. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
device.registry.list accepts 1 parameter: vendor. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for device.registry.list: 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 Apibase. Nothing to install.
device.registry.list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the device.registry.list 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 device.registry.list. 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.
device.registry.list is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue