bluetooth_connect · Sysprobe MCP: Risk & Policy

WHAT IT DOES

What bluetooth_connect does on Sysprobe

AI agents invoke bluetooth_connect 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_connect needs a policy

This tool triggers an external operation (establishing a Bluetooth connection to a device) whose effect depends on the MAC address argument. It is not purely destructive or financial, but it executes a system-level action with real-world side effects (network/device connectivity change), placing it in the Execute category.

From the tool's definition [ACTION] Connect to a paired Bluetooth device by MAC

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bluetooth_connect Rate-limited

bluetooth_connect 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_connect": {
      "limits": [
        {
          "counter": "bluetooth_connect_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_connect

What does the bluetooth_connect tool do? +

[ACTION] Connect to a paired Bluetooth device by MAC. 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_connect? +

Register the Sysprobe MCP server in PolicyLayer and add a rule for bluetooth_connect: 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_connect? +

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

Can I rate-limit bluetooth_connect? +

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

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

bluetooth_connect 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.