AI agents call bluetooth_status to retrieve information from Sysprobe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current Bluetooth adapter status information. It performs no modification, execution, or destructive action. It is a diagnostic query that returns state information, consistent with the 'Read' category (retrieves or queries data; no side effects). The low severity reflects minimal risk even if misused by an agent, as reading Bluetooth status has no adverse operational impact.
From the tool's definition Tool description states 'Bluetooth adapter status (powered, discoverable, pairable)' - queries current state without modification. Name and description indicate read-only retrieval of adapter properties.
Attacks that exploit this kind of access
Bluetooth adapter status (powered, discoverable, pairable). It is categorised as a Read tool in the Sysprobe MCP Server, which means it retrieves data without modifying state.
Register the Sysprobe MCP server in PolicyLayer and add a rule for bluetooth_status: 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 Sysprobe. Nothing to install.
bluetooth_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bluetooth_status 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 bluetooth_status. 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.
bluetooth_status is provided by the Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →