Start the sauna and set target temperature (40-110°C)
AI agents invoke start_sauna to trigger actions in Home Controller. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a command that causes external hardware (HUUM sauna) to perform an action. While starting a sauna is not inherently destructive or financial, it is an Execute action because it triggers a physical operation whose effects depend on the provided arguments (target temperature).
From the tool's definition Tool description states 'Start the sauna and set target temperature' — this actively triggers a physical device operation with parameters that control its behavior (temperature 40-110°C).
Attacks that exploit this kind of access
Start the sauna and set target temperature (40-110°C). It is categorised as a Execute tool in the Home Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Home Controller MCP server in PolicyLayer and add a rule for start_sauna: 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.
start_sauna is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_sauna 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 start_sauna. 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.
start_sauna 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 →