trigger_test_alarm · Nest Protect MCP Server MCP

WHAT IT DOES

What trigger_test_alarm does on Nest Protect MCP Server

AI agents invoke trigger_test_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 trigger_test_alarm needs a policy

This tool executes an external operation that activates a physical alarm on Nest Protect devices. While labeled as a 'test' function, it still causes an observable side effect (audible alarm) that is not reversible in real-time and could disrupt occupants or emergency services if misused by an AI agent.

From the tool's definition trigger_test_alarm: 'Trigger Test Alarm Ring' — triggers an external action (alarm activation) on physical devices whose effects depend on runtime arguments and execution context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_test_alarm Rate-limited

trigger_test_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": {
    "trigger_test_alarm": {
      "limits": [
        {
          "counter": "trigger_test_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 trigger_test_alarm

What does the trigger_test_alarm tool do? +

Trigger Test Alarm Ring. 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 trigger_test_alarm? +

Register the Nest Protect MCP Server MCP server in PolicyLayer and add a rule for trigger_test_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 trigger_test_alarm? +

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

Can I rate-limit trigger_test_alarm? +

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

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

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