Get current temperature data for a specific node/sensor. Defaults to environment (bme680) temperature. Use sensor_type='bme280' for internal/hardware temperature.
AI agents call get_node_temperature to retrieve information from Sage 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 sensor temperature data from Sage nodes without modifying, deleting, or triggering external operations. It is purely informational and poses minimal risk if misused—the worst outcome would be reading sensitive environmental or hardware data, which is a low-severity information disclosure risk.
From the tool's definition Tool name 'get_node_temperature' and description 'Get current temperature data' indicate a retrieval operation with no side effects. The mention of sensor type parameters confirms this is a query operation with no data modification or external execution.
Attacks that exploit this kind of access
Get current temperature data for a specific node/sensor. Defaults to environment (bme680) temperature. Use sensor_type='bme280' for internal/hardware temperature. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for get_node_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 Sage MCP Server. Nothing to install.
get_node_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_node_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_node_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_node_temperature is provided by the Sage MCP Server MCP server (waggle-sensor/sage-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 →