AI agents call get_heating_circuit_history 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.
The 'get_' prefix combined with 'history' indicates this tool retrieves past heating circuit data without modifying system state. This is a read operation with no side effects. Confidence is moderate rather than high due to missing tool description, but the naming convention is consistent with other read-only tools on this ZONT control server.
From the tool's definition Tool name contains 'get_' prefix and 'history' suffix, indicating data retrieval with no modification. Sibling tools on the same server (get_boiler_history, get_device_state, get_devices, get_events) follow the same read-only pattern.
Attacks that exploit this kind of access
get_heating_circuit_history. 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_heating_circuit_history: 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_heating_circuit_history 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_heating_circuit_history 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_heating_circuit_history. 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_heating_circuit_history 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 →