Set the temperature setpoint on a thermostat or zone. Supports single setpoint for heating/cooling systems, or separate low/high setpoints for heat pump systems. Changes take effect immediately.
AI agents use set_temperature to create or update resources in Plugwise — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugwise environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
setpoint | number | — | Temperature setpoint in Celsius for single-setpoint systems |
location_id | string | Yes | ID of the location/zone to control |
setpoint_low | number | — | Low temperature setpoint (heating) in Celsius for heat pump systems |
setpoint_high | number | — | High temperature setpoint (cooling) in Celsius for heat pump systems |
Parameters from the server's own tool schema.
This is a Write operation: it creates/modifies data (temperature setpoint) reversibly without permanent deletion or financial impact. While it affects physical systems, the change is not destructive and can be undone by setting a new value. Severity is medium because misuse could cause discomfort or minor HVAC inefficiency, but not data loss or critical infrastructure damage.
From the tool's definition Tool description states 'Set the temperature setpoint' and 'Changes take effect immediately.' This modifies thermostat/zone configuration but is reversible—a subsequent call can restore prior values.
Attacks that exploit this kind of access
Set the temperature setpoint on a thermostat or zone. Supports single setpoint for heating/cooling systems, or separate low/high setpoints for heat pump systems. Changes take effect immediately. It is categorised as a Write tool in the Plugwise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_temperature accepts 4 parameters: setpoint, location_id, setpoint_low, setpoint_high. Required: location_id. The full parameter table on this page comes from the server's own tool schema.
Register the Plugwise MCP server in PolicyLayer and add a rule for set_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 Plugwise. Nothing to install.
set_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_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_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_temperature is provided by the Plugwise MCP server (plugwise-mcp-server). 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 →