reboot_gateway · Plugwise MCP: Risk & Policy

WHAT IT DOES

What reboot_gateway does on Plugwise

AI agents invoke reboot_gateway to trigger actions in Plugwise. 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 reboot_gateway needs a policy

This is an Execute category tool because it triggers an external operation (gateway restart) whose effects depend on context and timing. While not destructive (data/configuration not lost), it has significant blast radius: it interrupts all home automation monitoring and control for 1-2 minutes, affecting all dependent systems and potentially user safety/comfort.

From the tool's definition Tool performs 'Reboot the Plugwise gateway' - a direct system operation that executes a restart command on network hardware.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_gateway Rate-limited

reboot_gateway 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": {
    "reboot_gateway": {
      "limits": [
        {
          "counter": "reboot_gateway_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 Plugwise, so you can run agents against it safely.

FAQ

Questions about reboot_gateway

What does the reboot_gateway tool do? +

Reboot the Plugwise gateway (use with caution). This will restart the gateway, temporarily interrupting all control and monitoring. The gateway will be offline for 1-2 minutes. Only use when necessary for troubleshooting. It is categorised as a Execute tool in the Plugwise MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reboot_gateway? +

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

What risk level is reboot_gateway? +

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

Can I rate-limit reboot_gateway? +

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

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

reboot_gateway is provided by the Plugwise MCP server (plugwise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.