ID of the location/zone to control
AI agents use set_preset to create or update resources in Plugwise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugwise MCP Server environment.
This tool creates or modifies thermostat presets—a reversible change to smart home state. It does not irreversibly delete data (not Destructive), execute arbitrary commands (not Execute), or move money (not Financial). The blast radius is medium: incorrect preset changes could cause discomfort or inefficient energy use, but are easily undone.
From the tool's definition Tool named 'set_preset' in a thermostat/temperature control context; description indicates it controls a location/zone, implying modification of temperature settings or climate presets.
Attacks that exploit this kind of access
ID of the location/zone to control. It is categorised as a Write tool in the Plugwise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plugwise MCP Server 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 MCP Server. 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 MCP server (tommertom/plugwise-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 →