get_temperature_summary

Get a summary of current temperature readings across all sensors. Defaults to environment (bme680) temperature. Use sensor_type='bme280' for internal/hardware temperature.

Server Sage MCP Server waggle-sensor/sage-mcp
Category Read
Risk class Low
Parameters 00 required

What get_temperature_summary does on Sage MCP Server

AI agents call get_temperature_summary 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.

Why get_temperature_summary needs a policy

This tool queries and retrieves temperature data from sensors without side effects. It is a straightforward data retrieval operation with no capability to modify, delete, or execute code. The severity is low because temperature readings are informational only and do not expose critical infrastructure or sensitive operations.

From the tool's definition Tool name 'get_temperature_summary' and description indicate retrieval of sensor data ('Get a summary of current temperature readings across all sensors'). No modification, deletion, or execution of external operations is described.

Questions about get_temperature_summary

What does the get_temperature_summary tool do? +

Get a summary of current temperature readings across all sensors. 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.

How do I enforce a policy on get_temperature_summary? +

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

What risk level is get_temperature_summary? +

get_temperature_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_temperature_summary? +

Yes. Add a rate_limit block to the get_temperature_summary 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 get_temperature_summary completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.