set_device_led · Nest Protect MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_device_led does on Nest Protect MCP Server

AI agents use set_device_led to create or update resources in Nest Protect MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nest Protect MCP Server environment.

WHY IT NEEDS A POLICY

Why set_device_led needs a policy

The tool modifies device settings (LED brightness) but does not delete data, execute arbitrary code, move money, or trigger irreversible actions. It is a straightforward Write operation that adjusts device parameters. Severity is low because LED brightness changes have minimal blast radius—they do not affect safety functionality, trigger emergency responses, or compromise critical home systems.

From the tool's definition Tool name 'set_device_led' and description 'Set Device LED Brightness' indicate creation or modification of device state (LED brightness level). This is a reversible configuration change to a Nest Protect device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_device_led Rate-limited

set_device_led stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_device_led": {
      "limits": [
        {
          "counter": "set_device_led_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_device_led

What does the set_device_led tool do? +

Set Device LED Brightness. It is categorised as a Write tool in the Nest Protect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_device_led? +

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

set_device_led is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_device_led? +

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

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

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