set_power · Buspirate MCP: Risk & Policy

WHAT IT DOES

What set_power does on Buspirate

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

Toggling a power supply on connected hardware can cause resets, data corruption, or damage to attached devices. This is an external hardware operation with real-world effects, making it Execute. The blast radius is high because disabling power unexpectedly can corrupt firmware, destroy in-progress operations, or damage sensitive components.

From the tool's definition 'Enable or disable the power supply' — controls hardware power state on a physical BusPirate device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_power Rate-limited

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

FAQ

Questions about set_power

What does the set_power tool do? +

Enable or disable the power supply. It is categorised as a Execute tool in the Buspirate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_power? +

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

What risk level is set_power? +

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

Can I rate-limit set_power? +

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

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

set_power is provided by the Buspirate MCP server (mplogas/buspirate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.