AI agents call get_energy_analysis 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 tool name begins with 'get_', which conventionally indicates retrieval without modification. All sibling tools are diagnostic or state-monitoring functions (get_devices, get_device_state, get_events, etc.), suggesting this tool follows the same read-only pattern for analyzing historical energy consumption data from the ZONT heating system. No indication of control, execution, or data mutation.
From the tool's definition Tool name 'get_energy_analysis' and its position among sibling tools (get_boiler_history, get_heating_circuit_history, get_events) suggests data retrieval.
Attacks that exploit this kind of access
get_energy_analysis. 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_energy_analysis: 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_energy_analysis 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_energy_analysis 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_energy_analysis. 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_energy_analysis 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 →