bluetooth_power · Sysprobe MCP: Risk & Policy

WHAT IT DOES

What bluetooth_power does on Sysprobe

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

This tool controls hardware state by toggling the Bluetooth adapter power. It triggers an external system operation with real effects (enabling/disabling hardware), fitting the Execute category. Misuse could disrupt Bluetooth connectivity across the system, warranting medium severity.

From the tool's definition [ACTION] Turn the Bluetooth adapter on or off.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bluetooth_power Rate-limited

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

FAQ

Questions about bluetooth_power

What does the bluetooth_power tool do? +

[ACTION] Turn the Bluetooth adapter on or off. It is categorised as a Execute tool in the Sysprobe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bluetooth_power? +

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

What risk level is bluetooth_power? +

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

Can I rate-limit bluetooth_power? +

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

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

bluetooth_power is provided by the Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.