Check index and cache status.
AI agents call check_index_status to retrieve information from Bluetooth Specifications MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only inspection of internal system state (index and cache status). It retrieves information but has no side effects, no destructive capability, and no ability to modify or execute operations. It is a diagnostic/monitoring tool, clearly in the Read category with low severity since misuse would only expose metadata about the search index.
From the tool's definition Tool name 'check_index_status' and description 'Check index and cache status' indicate a query operation that retrieves status information without modifying data or triggering external operations.
Attacks that exploit this kind of access
Check index and cache status. It is categorised as a Read tool in the Bluetooth Specifications MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bluetooth Specifications MCP Server MCP server in PolicyLayer and add a rule for check_index_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 Bluetooth Specifications MCP Server. Nothing to install.
check_index_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 check_index_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 check_index_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.
check_index_status is provided by the Bluetooth Specifications MCP Server MCP server (lmolina/mcp-bluetooth-specification). 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 →