Retrieves entities (or devices) of certain types. Can request multiple entity types at once. The return structure is a JSON string that contains the states of the requested entities. This data is exact. Whatever entities exist will be returned here. This is the primary tool for checking device ...
Part of the Rhombus Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get-entity-tool to retrieve information from Rhombus Node without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get-entity-tool only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get-entity-tool:
rules:
- action: allowSee the full Rhombus Node policy for all 30 tools.
Agents calling read-class tools like get-entity-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieves entities (or devices) of certain types. Can request multiple entity types at once. The return structure is a JSON string that contains the states of the requested entities. This data is exact. Whatever entities exist will be returned here. This is the primary tool for checking device health and connectivity status. Each device in the response includes a "connected" boolean field indicating whether it is currently online (true) or offline (false). When asked about device health, offline devices, or connectivity issues, use this tool to fetch all device types and check the "connected" field to identify which devices are offline or unreachable.. It is categorised as a Read tool in the Rhombus Node MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get-entity-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
get-entity-tool 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 get-entity-tool rule in your Intercept 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 Intercept policy for get-entity-tool. 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.
get-entity-tool is provided by the Rhombus Node MCP server (rhombus-node-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept