Get current temperature settings and available ranges for a refrigerator or freezer
AI agents call get_temperature_settings to retrieve information from Home Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only configuration information about appliance temperature parameters. It queries current state without creating, modifying, deleting, or executing any changes to devices or data. The action is purely informational with no blast radius if misused by an agent.
From the tool's definition Tool name 'get_temperature_settings' and description 'Get current temperature settings and available ranges' indicate retrieval of existing configuration data with no modification or side effects.
Attacks that exploit this kind of access
Get current temperature settings and available ranges for a refrigerator or freezer. It is categorised as a Read tool in the Home Controller MCP Server, which means it retrieves data without modifying state.
Register the Home Controller MCP server in PolicyLayer and add a rule for get_temperature_settings: 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 Home Controller. Nothing to install.
get_temperature_settings 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_settings 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_settings. 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_settings is provided by the Home Controller MCP server (winsthuang/home-controller). 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 →