AI agents call get_system_summary 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 name and context strongly suggest this retrieves summary information about the ZONT heating system state. Despite missing description, the naming convention and sibling tools indicate a read operation. No capability to modify, delete, or trigger actions is evident.
From the tool's definition Tool name 'get_system_summary' indicates data retrieval. Description is empty, lowering confidence. Sibling tools on this server (get_boiler_history, get_device_state, get_devices, get_events, get_energy_analysis) are all read-only queries; consistent pattern…
Attacks that exploit this kind of access
get_system_summary. 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_system_summary: 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_system_summary 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_system_summary 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_system_summary. 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_system_summary 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 →