hush_active_alarm · Nest Protect MCP Server MCP

WHAT IT DOES

What hush_active_alarm does on Nest Protect MCP Server

AI agents invoke hush_active_alarm to trigger actions in Nest Protect MCP Server. 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.

WHY IT NEEDS A POLICY

Why hush_active_alarm needs a policy

This tool executes a real-world action on a safety-critical device by silencing an active alarm. Suppressing a smoke or carbon monoxide alarm during an actual emergency could be life-threatening. It is not merely writing configuration data but triggering an operational command on external hardware. The blast radius is high because misuse could mute a legitimate life-safety warning.

From the tool's definition 'Silence Active Alarm Device' — actively triggers an external operation on a physical smoke/CO detector to suppress an ongoing alarm

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hush_active_alarm Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hush_active_alarm": {
      "limits": [
        {
          "counter": "hush_active_alarm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nest Protect MCP Server, so you can run agents against it safely.

FAQ

Questions about hush_active_alarm

What does the hush_active_alarm tool do? +

Silence Active Alarm Device. It is categorised as a Execute tool in the Nest Protect MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hush_active_alarm? +

Register the Nest Protect MCP Server MCP server in PolicyLayer and add a rule for hush_active_alarm: 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 Nest Protect MCP Server. Nothing to install.

What risk level is hush_active_alarm? +

hush_active_alarm is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hush_active_alarm? +

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

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

hush_active_alarm is provided by the Nest Protect MCP Server MCP server (sandraschi/nest-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.