scan_bluetooth

Scan for nearby BLE (Bluetooth Low Energy) devices. Returns device names, UUIDs, and signal strength (RSSI).

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/scan-bluetooth.md

WHAT IT DOES

What scan_bluetooth does on Iconnect

AI agents call scan_bluetooth to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why scan_bluetooth is rated Low

This tool retrieves Bluetooth device metadata from the local environment without triggering any actions on those devices, modifying system state, or executing external operations. The scan operation is passive discovery only, analogous to a network scan or list operation. The data returned (names, UUIDs, RSSI) is read-only sensor information.

From the tool's definition Tool description states it 'Scan[s] for nearby BLE devices' and 'Returns device names, UUIDs, and signal strength (RSSI)' — a purely informational operation with no state modification or command execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_bluetooth safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 Allowed

scan_bluetooth is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_bluetooth": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about scan_bluetooth

What does the scan_bluetooth tool do? +

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 Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scan_bluetooth? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is scan_bluetooth? +

scan_bluetooth is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scan_bluetooth? +

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.

How do I block scan_bluetooth completely? +

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.

What MCP server provides scan_bluetooth? +

scan_bluetooth is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →