Get statistics for entities and relationships in a zone.
AI agents call zone_stats to retrieve information from Elastic Brain ZH without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about existing data structures (entities and relationships) within a memory zone. It has no side effects, does not execute code or external operations, does not modify data, and does not delete anything. It is a straightforward read/query operation with minimal security risk even if invoked by an AI agent.
From the tool's definition Tool name 'zone_stats' and description 'Get statistics for entities and relationships in a zone' indicate a query operation that retrieves aggregated data without modifying or deleting anything.
Attacks that exploit this kind of access
Get statistics for entities and relationships in a zone. It is categorised as a Read tool in the Elastic Brain ZH MCP Server, which means it retrieves data without modifying state.
Register the Elastic Brain ZH MCP server in PolicyLayer and add a rule for zone_stats: 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 Elastic Brain ZH. Nothing to install.
zone_stats 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 zone_stats 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 zone_stats. 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.
zone_stats is provided by the Elastic Brain ZH MCP server (tocharianou/elastic-brain-zh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →