This record as markdown: /tools/heznpc-airmcp/disconnect-bluetooth.md
What disconnect_bluetooth does on AirMCP
AI agents invoke disconnect_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.
Why disconnect_bluetooth is rated High
This tool triggers an external system operation — disconnecting a Bluetooth Low Energy device — which has real-world effects (severing a hardware connection) that depend on the provided UUID argument. It is not a simple data read or write, but an action that affects device state. Misuse could disconnect critical peripherals (e.g., medical devices, keyboards, mice), making it medium severity.
From the tool's definition Disconnect a BLE device by its UUID
Attacks that exploit this kind of access
The rule that runs disconnect_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 disconnect_bluetooth, this is the rule to start with:
disconnect_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every disconnect_bluetooth call is checked against it from then on.
Questions about disconnect_bluetooth
Disconnect a BLE device by its UUID. 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.
Register the Air MCP server in PolicyLayer and add a rule for disconnect_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.
disconnect_bluetooth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the disconnect_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.
Set action: deny in the PolicyLayer policy for disconnect_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.
disconnect_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.
More on Air, and thousands of servers like it.
This server
Across the catalogue