ID of the thermostat device to query
AI agents call get_temperature_offset to retrieve information from Plugwise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data from a smart home device without side effects. It is a read-only query operation that poses minimal security risk—an agent misusing it could only expose temperature calibration offsets, which is non-sensitive information with no impact on device control, data destruction, or financial systems.
From the tool's definition Tool name 'get_temperature_offset' and description indicate it queries a thermostat device parameter. The verb 'get' and the passive retrieval nature (reading an offset value) with no mention of modification, deletion, or external execution.
Attacks that exploit this kind of access
ID of the thermostat device to query. It is categorised as a Read tool in the Plugwise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plugwise MCP Server 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 MCP Server. 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 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 →