AI agents use set_preset 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 |
|---|---|---|---|
preset | string | Yes | Preset name (e.g., home, away, sleep, vacation, no_frost) |
location_id | string | Yes | ID of the location/zone to control |
Parameters from the server's own tool schema.
The tool modifies HVAC preset modes on thermostats/zones, which are configuration changes with reversible effects. This qualifies as Write rather than Execute because it applies predefined presets rather than executing arbitrary code, and the changes are reversible (can be set back to previous preset).
From the tool's definition Tool description states 'Set the preset mode' which modifies thermostat/zone configuration by applying predefined settings. This is a write operation that changes system state (temperature setpoints and behaviors).
Attacks that exploit this kind of access
Set the preset mode on a thermostat or zone (e.g., home, away, sleep, vacation). Presets apply predefined temperature settings and behaviors configured in your Plugwise system. 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_preset accepts 2 parameters: preset, location_id. Required: preset, 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_preset: 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_preset 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_preset 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_preset. 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_preset 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 →