search_entities

Fuzzy search entities by entity_id, friendly_name, and device_id.

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/search-entities.md

WHAT IT DOES

What search_entities does on Ha Nexus Agent

AI agents call search_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 search_entities is rated Low

This is a passive information retrieval tool that queries Home Assistant's entity registry to find matching entities. It has no side effects, cannot modify data, execute commands, or cause destructive changes. The fuzzy search capability is a standard read operation with minimal blast radius if misused—worst case returns unexpected search results without system impact.

From the tool's definition Tool description explicitly states it performs a 'Fuzzy search' operation on entities. Verb 'search' indicates data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_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 search_entities, this is the rule to start with:

search_entities Allowed

search_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": {
    "search_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 search_entities call is checked against it from then on.

FAQ

Questions about search_entities

What does the search_entities tool do? +

Fuzzy search entities by entity_id, friendly_name, and device_id. 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 search_entities? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for search_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 search_entities? +

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

Can I rate-limit search_entities? +

Yes. Add a rate_limit block to the search_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 search_entities completely? +

Set action: deny in the PolicyLayer policy for search_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 search_entities? +

search_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 276 Ha Nexus Agent tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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