toggle_device_power · Bond MCP Server MCP: Risk & Policy

WHAT IT DOES

What toggle_device_power does on Bond MCP Server

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

This tool triggers an external operation on a physical smart home device, changing its power state. It is not purely a read, write, or destructive action — it executes a command that causes a real-world effect (turning a device on or off). The blast radius is medium since misuse could disrupt smart home devices like fans, lights, or shades, but no data is deleted and no financial transactions occur.

From the tool's definition Toggle power state of a Bond device (on/off)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggle_device_power Rate-limited

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

FAQ

Questions about toggle_device_power

What does the toggle_device_power tool do? +

Toggle power state of a Bond device (on/off). It is categorised as a Execute tool in the Bond 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 toggle_device_power? +

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

What risk level is toggle_device_power? +

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

Can I rate-limit toggle_device_power? +

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

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

toggle_device_power is provided by the Bond MCP Server MCP server (madorn/bond-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

toggle_device_power is one line of Bond MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →