embeddings_rabitq_build
Build RaBitQ 1-bit quantized index from stored embeddings (32× compression). Pre-filters candidates via Hamming scan before exact rerank. Use when text similarity matters beyond keyword match — native Grep finds exact strings, embeddings find meaning. Pair with memory_store / agentdb_pattern-sear...
This record as markdown: /tools/io-github-ruvnet-claude-flow/embeddings-rabitq-build.md
What embeddings_rabitq_build does on Claude Flow
AI agents invoke embeddings_rabitq_build to trigger actions in Claude Flow. 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 embeddings_rabitq_build is rated High
This tool executes a complex indexing and vector search operation (building a quantized embedding index, performing Hamming scans, and reranking). While it does not directly delete data or execute arbitrary code, it triggers a computational pipeline with external effects on the vector search system.
From the tool's definition Build RaBitQ 1-bit quantized index from stored embeddings... Pre-filters candidates via Hamming scan before exact rerank. Use when text similarity matters beyond keyword match.
Attacks that exploit this kind of access
The rule that runs embeddings_rabitq_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For embeddings_rabitq_build, this is the rule to start with:
embeddings_rabitq_build 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 Claude Flow, apply this rule, and every embeddings_rabitq_build call is checked against it from then on.
Questions about embeddings_rabitq_build
Build RaBitQ 1-bit quantized index from stored embeddings (32× compression). Pre-filters candidates via Hamming scan before exact rerank. Use when text similarity matters beyond keyword match — native Grep finds exact strings, embeddings find meaning. Pair with memory_store / agentdb_pattern-search to land the vector against your knowledge base. For literal symbol search, native Grep is faster. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for embeddings_rabitq_build: 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 Claude Flow. Nothing to install.
embeddings_rabitq_build 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 embeddings_rabitq_build 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 embeddings_rabitq_build. 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.
embeddings_rabitq_build is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
Across the catalogue