android_set_bluetooth · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_set_bluetooth does on DevLab MCP Suite

AI agents invoke android_set_bluetooth to trigger actions in DevLab MCP Suite. 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 IT NEEDS A POLICY

Why android_set_bluetooth needs a policy

This tool modifies the state of the Android device's Bluetooth hardware. It does not read data, write files, delete data, or move money — it executes a system-level state change on an external device. Misuse could disrupt connectivity or enable unauthorized pairing opportunities, giving it medium severity.

From the tool's definition 'Enable or disable Bluetooth on the device' — triggers an external device state change (toggling Bluetooth radio on/off)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_set_bluetooth Rate-limited

android_set_bluetooth 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "android_set_bluetooth": {
      "limits": [
        {
          "counter": "android_set_bluetooth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_set_bluetooth

What does the android_set_bluetooth tool do? +

Enable or disable Bluetooth on the device. Best-effort: may be blocked by OEM restrictions or Android version. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_set_bluetooth? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_set_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 DevLab MCP Suite. Nothing to install.

What risk level is android_set_bluetooth? +

android_set_bluetooth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit android_set_bluetooth? +

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

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

android_set_bluetooth is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.