search_specifications
AI agents call search_specifications 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 retrieves and queries data from indexed Bluetooth specification documents using hybrid search (BM25 + semantic embeddings). It has no side effects, does not modify data, execute code, or perform destructive operations. It is purely a read/retrieval operation returning search results with citations. The empty description does not change this assessment given the clear context from the server description.
From the tool's definition Tool name 'search_specifications' combined with server description stating 'natural language search over Bluetooth specification PDFs' and 'returning precise answers with citations'.
Attacks that exploit this kind of access
search_specifications. 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 search_specifications: 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.
search_specifications 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 search_specifications 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 search_specifications. 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.
search_specifications 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 →