AI agents call get_temperature 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 device/zone to read temperature from |
Parameters from the server's own tool schema.
This tool queries thermostat/zone temperature state and returns the results. No data is modified, deleted, executed, or created. It is a pure read operation typical of IoT device status queries. The low severity reflects that temperature telemetry exposure has minimal security impact compared to control operations available on this server (e.g., control_switch, reboot_gateway).
From the tool's definition Tool retrieves current room temperature and setpoint data with no modification capability. The description explicitly states it 'returns' measurements with no side effects. The name 'get_temperature' and verb pattern indicates data retrieval only.
Attacks that exploit this kind of access
Get current room temperature and setpoint for a specific thermostat or zone. Returns both the measured temperature and the target setpoint. It is categorised as a Read tool in the Plugwise MCP Server, which means it retrieves data without modifying state.
get_temperature 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: 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 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 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. 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 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 →