control_switch · Plugwise MCP Server MCP: Risk & Policy

WHAT IT DOES

What control_switch does on Plugwise MCP Server

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

Controlling a switch triggers real-world physical effects (turning devices on/off), which is an external operation whose effects depend on arguments. This falls under Execute as it triggers external operations. Misuse could affect heating, appliances, or other critical home systems. Confidence is slightly reduced because the description is uninformative and doesn't explicitly detail the action taken.

From the tool's definition 'control_switch' — controls a switch device; description only states 'ID of the appliance/device to control' which implies toggling/operating physical smart home switches

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

control_switch Rate-limited

control_switch 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": {
    "control_switch": {
      "limits": [
        {
          "counter": "control_switch_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about control_switch

What does the control_switch tool do? +

ID of the appliance/device to control. It is categorised as a Execute tool in the Plugwise 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 control_switch? +

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

What risk level is control_switch? +

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

Can I rate-limit control_switch? +

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

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

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