device.registry.state
Read the current state (data points) of one physical device the calling agent owns via a linked vendor connection. Requires connection_id (from device.list) and device_id.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/device.registry.state.md
What device.registry.state does on Apibase
AI agents call device.registry.state 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 |
|---|---|---|---|
device_id | string | Yes | The vendor's device id (from device.list) |
connection_id | string | Yes | Your device-connection id from /connect/device/connections |
Parameters from the server's own tool schema.
Why device.registry.state is rated Low
Retrieves device state data without modification, deletion, or external operation execution.
From the tool's definition Read the current state (data points) of one physical device
Attacks that exploit this kind of access
The rule that runs device.registry.state 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.state, this is the rule to start with:
device.registry.state 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.state call is checked against it from then on.
Questions about device.registry.state
Read the current state (data points) of one physical device the calling agent owns via a linked vendor connection. Requires connection_id (from device.list) and device_id. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
device.registry.state accepts 2 parameters: device_id, connection_id. Required: device_id, connection_id. 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.state: 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.state 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.state 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.state. 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.state 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