Get the temperature offset (calibration) for a thermostat device. The offset is used to calibrate the temperature sensor if it reads incorrectly. Returns the current offset value and its valid range.
AI agents call get_temperature_offset to retrieve information from Plugwise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id | string | Yes | ID of the thermostat device to query |
Parameters from the server's own tool schema.
This tool retrieves configuration data (temperature offset/calibration value) without modifying, deleting, or executing any changes to the system. It is a simple GET-like operation on device settings, posing minimal risk if called by an AI agent.
From the tool's definition Tool description states 'Get the temperature offset' and 'Returns the current offset value' — this is a retrieval operation with no side effects. The action is purely informational, querying calibration data from a thermostat device.
Attacks that exploit this kind of access
Get the temperature offset (calibration) for a thermostat device. The offset is used to calibrate the temperature sensor if it reads incorrectly. Returns the current offset value and its valid range. It is categorised as a Read tool in the Plugwise MCP Server, which means it retrieves data without modifying state.
get_temperature_offset accepts 1 parameter: device_id. Required: device_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 get_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.
get_temperature_offset is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →