run_safety_test · Nest Protect MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_safety_test does on Nest Protect MCP Server

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

This tool triggers execution of a test procedure on Nest Protect devices. While the test itself is designed to be non-destructive (safety tests are normal maintenance), it executes an external operation whose effects depend on device state and configuration.

From the tool's definition Tool name contains 'run' and description states 'Execute Device Safety Test' — both indicate execution of an operation on physical safety devices (smoke/CO detectors).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_safety_test Rate-limited

run_safety_test 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": {
    "run_safety_test": {
      "limits": [
        {
          "counter": "run_safety_test_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 run_safety_test

What does the run_safety_test tool do? +

Execute Device Safety Test. 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 run_safety_test? +

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

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

Can I rate-limit run_safety_test? +

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

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

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