AI agents call get_web_element_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.
This tool retrieves historical state information about a custom control element within the ZONT heating system. It performs a passive query with no side effects—it neither modifies system state, executes commands, deletes data, nor commits financial transactions. The low severity reflects that exposing historical heating control state data poses minimal risk to the system, even if accessed by an unauthorized agent.
From the tool's definition Tool name and description (in Russian: 'Get history of states of a custom control element') both indicate retrieval of historical state data. The verb 'get/получить' and context 'история' (history) confirm read-only query operations.
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_web_element_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_web_element_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_web_element_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_web_element_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_web_element_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 →