find_related

Return device, area, floor, sibling entities (same device), and area-mates for an entity.

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/find-related.md

WHAT IT DOES

What find_related does on Ha Nexus Agent

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

This tool queries and retrieves existing smart home topology and relationship metadata. It performs no modifications, deletions, or external operations. The blast radius is minimal—an AI agent using this tool can only discover what entities are related to a given entity, which is informational and non-harmful.

From the tool's definition Tool 'find_related' returns/retrieves data about device relationships, areas, floors, and entity associations. The verb 'Return' and the purely informational nature (device/area/floor metadata discovery) indicate read-only querying with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

find_related Allowed

find_related 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": {
    "find_related": {}
  }
}

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 find_related call is checked against it from then on.

FAQ

Questions about find_related

What does the find_related tool do? +

Return device, area, floor, sibling entities (same device), and area-mates for an entity. 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 find_related? +

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

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

Can I rate-limit find_related? +

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

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

find_related 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

The MCP Attack Database →

Guides

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