wavexis_bluetooth_device_list

List emulated Bluetooth devices.

SERVERWavexis SOURCEMathiasPaulenko/wavexis-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/wavexis-mcp/wavexis-bluetooth-device-list.md

WHAT IT DOES

What wavexis_bluetooth_device_list does on Wavexis

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

RISK

Why wavexis_bluetooth_device_list is rated Low

This tool retrieves information about emulated Bluetooth devices without modifying, executing, or deleting anything. It is a passive read operation. Severity is low because listing devices exposes only configuration/state information without enabling direct control or harmful actions by itself.

From the tool's definition Tool name 'wavexis_bluetooth_device_list' and description 'List emulated Bluetooth devices' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wavexis_bluetooth_device_list safely

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

wavexis_bluetooth_device_list Allowed

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

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

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

FAQ

Questions about wavexis_bluetooth_device_list

What does the wavexis_bluetooth_device_list tool do? +

List emulated Bluetooth devices. It is categorised as a Read tool in the Wavexis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wavexis_bluetooth_device_list? +

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

What risk level is wavexis_bluetooth_device_list? +

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

Can I rate-limit wavexis_bluetooth_device_list? +

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

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

wavexis_bluetooth_device_list is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wavexis, and thousands of servers like it.

This server

All 195 Wavexis tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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