scan_bluetooth
Scan for nearby BLE (Bluetooth Low Energy) devices. Returns device names, UUIDs, and signal strength (RSSI).
This record as markdown: /tools/heznpc-airmcp/scan-bluetooth.md
What scan_bluetooth does on AirMCP
AI agents call scan_bluetooth to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_bluetooth is rated Low
Scanning for Bluetooth devices is a passive information-gathering operation with no side effects. The tool queries the state of the Bluetooth environment and returns metadata about discoverable devices, which is characteristic of Read category tools. Severity is low because discovering nearby device identities poses minimal security risk compared to actually connecting to or controlling those devices.
From the tool's definition Tool performs a scan operation that 'returns device names, UUIDs, and signal strength' — it retrieves information about nearby BLE devices without modifying, executing commands on, or controlling any Bluetooth devices.
Attacks that exploit this kind of access
The rule that runs scan_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 scan_bluetooth, this is the rule to start with:
scan_bluetooth is read-only, so it stays allowed. 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 scan_bluetooth call is checked against it from then on.
Questions about scan_bluetooth
Scan for nearby BLE (Bluetooth Low Energy) devices. Returns device names, UUIDs, and signal strength (RSSI). It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for scan_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.
scan_bluetooth is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_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 scan_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.
scan_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