get_device_entities

Get all HA entities belonging to an ESPHome device (match by name/slug).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/get-device-entities.md

WHAT IT DOES

What get_device_entities does on Ha Nexus Agent

AI agents call get_device_entities to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_device_entities is rated Low

This tool queries and retrieves entity information from Home Assistant for a specific ESPHome device. The verb 'Get' and the absence of any modification, deletion, or execution language confirms this is a read-only data retrieval operation. While the broader server provides 'full control of your smart home', this specific tool performs only information lookup with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_device_entities' and description 'Get all HA entities belonging to an ESPHome device' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_device_entities safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_device_entities, this is the rule to start with:

get_device_entities Allowed

get_device_entities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_entities": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every get_device_entities call is checked against it from then on.

FAQ

Questions about get_device_entities

What does the get_device_entities tool do? +

Get all HA entities belonging to an ESPHome device (match by name/slug). It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_device_entities? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_device_entities: 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 Ha Nexus Agent. Nothing to install.

What risk level is get_device_entities? +

get_device_entities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_device_entities? +

Yes. Add a rate_limit block to the get_device_entities 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.

How do I block get_device_entities completely? +

Set action: deny in the PolicyLayer policy for get_device_entities. 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.

What MCP server provides get_device_entities? +

get_device_entities is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 309 Ha Nexus Agent tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →