connect_bluetooth

Connect to a BLE device by its UUID. The UUID can be obtained from scan_bluetooth results.

SERVERAirMCP SOURCEairmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/connect-bluetooth.md

WHAT IT DOES

What connect_bluetooth does on AirMCP

AI agents invoke connect_bluetooth to trigger actions in AirMCP. 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.

RISK

Why connect_bluetooth is rated High

Connecting to a Bluetooth device is an external system operation that initiates a hardware pairing/connection. It is not a simple read, nor does it delete data, but it executes a system-level action with real-world effects (connecting to potentially unknown or malicious devices, enabling data transfer channels).

From the tool's definition Connect to a BLE device by its UUID — triggers an external hardware/system operation (Bluetooth connection) whose effects depend on the provided UUID argument

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs connect_bluetooth safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For connect_bluetooth, this is the rule to start with:

connect_bluetooth Rate-limited

connect_bluetooth 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": {
    "connect_bluetooth": {
      "limits": [
        {
          "counter": "connect_bluetooth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every connect_bluetooth call is checked against it from then on.

FAQ

Questions about connect_bluetooth

What does the connect_bluetooth tool do? +

Connect to a BLE device by its UUID. The UUID can be obtained from scan_bluetooth results. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_bluetooth? +

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

What risk level is connect_bluetooth? +

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

Can I rate-limit connect_bluetooth? +

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

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

connect_bluetooth is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools → High-risk tools on this server →

Across the catalogue

adb_connect_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →