Set the domestic hot water (DHW) heating mode for systems with hot water control. Auto mode follows the schedule, boost mode provides immediate hot water heating, comfort mode maintains higher temperature, and off mode disables DHW heating.
AI agents use set_dhw_mode 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 |
|---|---|---|---|
mode | string | Yes | DHW mode: "auto" follows schedule, "boost" for immediate heating, "comfort" for higher temperature, "off" to disable |
Parameters from the server's own tool schema.
This tool modifies the operational mode of a hot water heating system. It changes a configuration/state setting (heating mode) which is reversible — the mode can be changed back. It does not irreversibly delete data, execute arbitrary code, or involve financial transactions. Misuse could cause discomfort or energy waste, warranting medium severity.
From the tool's definition Set the domestic hot water (DHW) heating mode... Auto mode follows the schedule, boost mode provides immediate hot water heating, comfort mode maintains higher temperature, and off mode disables DHW heating.
Attacks that exploit this kind of access
Set the domestic hot water (DHW) heating mode for systems with hot water control. Auto mode follows the schedule, boost mode provides immediate hot water heating, comfort mode maintains higher temperature, and off mode disables DHW heating. 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_dhw_mode accepts 1 parameter: mode. Required: mode. 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_dhw_mode: 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_dhw_mode 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_dhw_mode 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_dhw_mode. 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_dhw_mode 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 →