AI agents use set_target_temperature to create or update resources in Zont — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zont environment.
The tool name strongly suggests it changes a target temperature value in the ZONT heating system, which is a write operation. While the description is empty (lowering confidence), the name and server context (heating control system) indicate this modifies device state. Misuse could affect physical comfort or safety (e.g., setting dangerously high or low temperatures), warranting high severity.
From the tool's definition Tool name 'set_target_temperature' implies modifying a temperature setpoint in a heating system.
Attacks that exploit this kind of access
set_target_temperature. It is categorised as a Write tool in the Zont MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zont MCP server in PolicyLayer and add a rule for set_target_temperature: 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.
set_target_temperature is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_target_temperature 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 set_target_temperature. 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.
set_target_temperature 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 →