AI agents call get_radio_sensor_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.
Based on naming convention and context of similar tools on the server, this tool retrieves historical data about radio sensors from the ZONT heating system. No modification, deletion, or external execution is indicated. The 'get' prefix and sibling tools confirm this is a data retrieval operation with no capacity to modify system state.
From the tool's definition Tool name is 'get_radio_sensor_history' with 'get' prefix indicating retrieval. Description is empty but sibling tools like 'get_boiler_history', 'get_device_state', and 'get_events' are all Read operations that retrieve historical data without side effects.
Attacks that exploit this kind of access
get_radio_sensor_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_radio_sensor_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_radio_sensor_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_radio_sensor_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_radio_sensor_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_radio_sensor_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 →