get_bluetooth_state

Check whether Bluetooth is powered on, off, or unauthorized.

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/get-bluetooth-state.md

WHAT IT DOES

What get_bluetooth_state does on Iconnect

AI agents call get_bluetooth_state 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 get_bluetooth_state is rated Low

This tool performs a simple information retrieval operation—checking the state of a system component. It has no side effects, does not execute commands, does not modify data, and does not trigger external operations. The action verb 'Check' and the passive nature of the description confirm this is a Read category tool.

From the tool's definition Tool name 'get_bluetooth_state' and description 'Check whether Bluetooth is powered on, off, or unauthorized' indicate a read-only query operation that retrieves the current state of Bluetooth without modifying or controlling it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_bluetooth_state 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 get_bluetooth_state, this is the rule to start with:

get_bluetooth_state Allowed

get_bluetooth_state 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": {
    "get_bluetooth_state": {}
  }
}

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 get_bluetooth_state call is checked against it from then on.

FAQ

Questions about get_bluetooth_state

What does the get_bluetooth_state tool do? +

Check whether Bluetooth is powered on, off, or unauthorized. 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 get_bluetooth_state? +

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

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

Can I rate-limit get_bluetooth_state? +

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

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

get_bluetooth_state 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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