set_temperature_offset · Plugwise MCP: Risk & Policy

WHAT IT DOES

What set_temperature_offset does on Plugwise

AI agents use set_temperature_offset 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.

PARAMETERS

Parameter	Type	Required	Description
`offset`	number	Yes	Temperature offset in °C (can be positive or negative)
`device_id`	string	Yes	ID of the thermostat device

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why set_temperature_offset needs a policy

This tool modifies thermostat calibration settings, which is a reversible configuration change. While not destructive (can be undone by setting a different offset), it goes beyond read-only access and constitutes a Write operation.

From the tool's definition Tool description states it 'Set[s] the temperature offset (calibration) for a thermostat device' - a direct modification operation that changes device configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_temperature_offset Rate-limited

set_temperature_offset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_temperature_offset": {
      "limits": [
        {
          "counter": "set_temperature_offset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Plugwise, so you can run agents against it safely.

FAQ

Questions about set_temperature_offset

What does the set_temperature_offset tool do? +

Set the temperature offset (calibration) for a thermostat device. This adjusts the measured temperature by a fixed offset. 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.

What parameters does set_temperature_offset accept? +

set_temperature_offset accepts 2 parameters: offset, device_id. Required: offset, device_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_temperature_offset? +

Register the Plugwise MCP server in PolicyLayer and add a rule for set_temperature_offset: 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.

What risk level is set_temperature_offset? +

set_temperature_offset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_temperature_offset? +

Yes. Add a rate_limit block to the set_temperature_offset 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.

How do I block set_temperature_offset completely? +

Set action: deny in the PolicyLayer policy for set_temperature_offset. 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.

What MCP server provides set_temperature_offset? +

set_temperature_offset 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.