search_devices
Fuzzy search devices by name, name_by_user, manufacturer, and model.
This record as markdown: /tools/fistacho-ha-nexus-agent/search-devices.md
What search_devices does on Ha Nexus Agent
AI agents call search_devices 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.
Why search_devices is rated Low
This is a retrieval-only operation that searches existing data and returns results with no side effects. It does not create, modify, delete, or execute any actions on the smart home system. The search operation is inherently non-destructive and poses minimal security risk, though it could potentially leak information about devices in a system if accessed by an unauthorized party.
From the tool's definition The tool description explicitly states it performs 'Fuzzy search devices' without any modification, creation, deletion, or execution capabilities. It only retrieves and queries device information by name, user-assigned name, manufacturer, and model.
Attacks that exploit this kind of access
The rule that runs search_devices 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_devices, this is the rule to start with:
search_devices 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 Ha Nexus Agent, apply this rule, and every search_devices call is checked against it from then on.
Questions about search_devices
Fuzzy search devices by name, name_by_user, manufacturer, and model. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for search_devices: 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.
search_devices 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 search_devices 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 search_devices. 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.
search_devices 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.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue