AI agents call get_guard_zones to retrieve information from Zont without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists the current state of guard zones (security zones) on a heating device. It performs a read-only query operation with no side effects, no data modification, and no execution of external commands. The blast radius of misuse is minimal—an attacker gains visibility into security zone configuration but cannot arm/disarm zones or control the heating system itself.
From the tool's definition Tool name 'get_guard_zones' and description 'Get list of guard zones for device with current state (guard on/off)' indicates a retrieval operation that queries security zone status without modifying any state or triggering actions.
Attacks that exploit this kind of access
Получить список охранных зон устройства с текущим состоянием (охрана вкл/выкл). It is categorised as a Read tool in the Zont MCP Server, which means it retrieves data without modifying state.
Register the Zont MCP server in PolicyLayer and add a rule for get_guard_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 Zont. Nothing to install.
get_guard_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 get_guard_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 get_guard_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.
get_guard_zones is provided by the Zont MCP server (mab2908/zont-mcp). 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 →