list_persons_in_zone

List person.* entities currently inside the given zone (matched on friendly_name → state).

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/list-persons-in-zone.md

WHAT IT DOES

What list_persons_in_zone does on Ha Nexus Agent

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

This tool retrieves location data about persons in a zone by matching friendly names to states. It is a read-only query with no capacity to modify, delete, execute code, or trigger actions. The blast radius of misuse is minimal — an attacker gains visibility into occupancy/location information but cannot control devices, delete data, or perform financial transactions.

From the tool's definition Tool description states 'List `person.*` entities currently inside the given zone' — a query operation that retrieves state information with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_persons_in_zone Allowed

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

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

FAQ

Questions about list_persons_in_zone

What does the list_persons_in_zone tool do? +

List person.* entities currently inside the given zone (matched on friendly_name → state). 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 list_persons_in_zone? +

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

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

Can I rate-limit list_persons_in_zone? +

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

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

list_persons_in_zone 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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