wavexis_bluetooth_device_disconnect
Stop Bluetooth emulation.
This record as markdown: /tools/wavexis-mcp/wavexis-bluetooth-device-disconnect.md
What wavexis_bluetooth_device_disconnect does on Wavexis
AI agents invoke wavexis_bluetooth_device_disconnect to trigger actions in Wavexis. 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 wavexis_bluetooth_device_disconnect is rated High
This tool stops an active Bluetooth emulation session in the browser automation context. It triggers an external operational change (halting emulation), which is an action with side effects beyond simple data retrieval or writing. It doesn't delete data irreversibly, but it does execute a state-changing operation on the browser environment.
From the tool's definition 'Stop Bluetooth emulation' — triggers an external browser/device operation that changes emulation state
Attacks that exploit this kind of access
The rule that runs wavexis_bluetooth_device_disconnect 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_disconnect, this is the rule to start with:
wavexis_bluetooth_device_disconnect 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 Wavexis, apply this rule, and every wavexis_bluetooth_device_disconnect call is checked against it from then on.
Questions about wavexis_bluetooth_device_disconnect
Stop Bluetooth emulation. It is categorised as a Execute tool in the Wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_bluetooth_device_disconnect: 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.
wavexis_bluetooth_device_disconnect 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 wavexis_bluetooth_device_disconnect 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 wavexis_bluetooth_device_disconnect. 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.
wavexis_bluetooth_device_disconnect 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.
More on Wavexis, and thousands of servers like it.
Across the catalogue