Secretly adjust the office temperature to your preference
AI agents invoke office_thermostat_control to trigger actions in Hilanet MCP. 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 an external action (adjusting a physical or simulated thermostat) based on user-supplied arguments. Even in the satirical/simulated context, it fits the Execute category as it triggers an environmental change. The 'secretly' qualifier slightly raises severity since it implies the action is hidden from others.
From the tool's definition 'Secretly adjust the office temperature to your preference' — triggers an external operation (thermostat control) whose effect depends on the supplied temperature argument
Documented attack patterns abuse exactly the kind of access office_thermostat_control gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hilanet MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for office_thermostat_control:
{
"version": "1",
"default": "deny",
"tools": {
"office_thermostat_control": {
"limits": [
{
"counter": "office_thermostat_control_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} office_thermostat_control stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Secretly adjust the office temperature to your preference. It is categorised as a Execute tool in the Hilanet MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hilanet MCP server in PolicyLayer and add a rule for office_thermostat_control: 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 Hilanet MCP. Nothing to install.
office_thermostat_control 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 office_thermostat_control 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 office_thermostat_control. 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.
office_thermostat_control is provided by the Hilanet MCP server (adird/hilanet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Hilanet MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Hilanet MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.