turn_on · Switcher MCP Server MCP: Risk & Policy

WHAT IT DOES

What turn_on does on Switcher MCP Server

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

This tool triggers an external physical operation — turning on a Switcher KIS device (likely a smart switch/boiler/electrical appliance). It causes a real-world side effect (powering on hardware) that could pose safety or energy risks if misused. It is not merely writing data but executing a control command on physical infrastructure, making Execute the appropriate category.

From the tool's definition Turn on a Switcher device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turn_on Rate-limited

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

FAQ

Questions about turn_on

What does the turn_on tool do? +

Turn on a Switcher device. It is categorised as a Execute tool in the Switcher 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 turn_on? +

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

What risk level is turn_on? +

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

Can I rate-limit turn_on? +

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

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

turn_on is provided by the Switcher MCP Server MCP server (liebstein/switcher-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.