list_zones
List all zone.* entities with latitude/longitude/radius/friendly_name/passive.
This record as markdown: /tools/fistacho-ha-nexus-agent/list-zones.md
What list_zones does on Ha Nexus Agent
AI agents call list_zones 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 list_zones is rated Low
This tool queries and returns zone entity information (coordinates, names, settings) with no capability to create, modify, delete, or execute actions. It is a pure read/retrieval operation with minimal security impact even if misused by an agent.
From the tool's definition 'List all `zone.*` entities with latitude/longitude/radius/friendly_name/passive' — retrieves zone entity data without modification.
Attacks that exploit this kind of access
The rule that runs list_zones 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_zones, this is the rule to start with:
list_zones 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 list_zones call is checked against it from then on.
Questions about list_zones
List all zone.* entities with latitude/longitude/radius/friendly_name/passive. 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 list_zones: 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.
list_zones 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 list_zones 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 list_zones. 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.
list_zones 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