embeddings_rabitq_status
Get RaBitQ quantized index status — availability, vector count, compression ratio 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 l...
This record as markdown: /tools/io-github-ruvnet-claude-flow/embeddings-rabitq-status.md
What embeddings_rabitq_status does on Claude Flow
AI agents call embeddings_rabitq_status to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why embeddings_rabitq_status is rated Low
This tool queries metadata and state information (availability, vector count, compression ratio) from a vector index. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is purely informational retrieval, making it a Read category tool. Severity is low because misuse cannot cause harm — it merely returns status information.
From the tool's definition Tool name and description: 'Get RaBitQ quantized index status — availability, vector count, compression ratio'.
Attacks that exploit this kind of access
The rule that runs embeddings_rabitq_status 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_status, this is the rule to start with:
embeddings_rabitq_status is read-only, so it stays allowed. 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_status call is checked against it from then on.
Questions about embeddings_rabitq_status
Get RaBitQ quantized index status — availability, vector count, compression ratio 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 Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for embeddings_rabitq_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 Claude Flow. Nothing to install.
embeddings_rabitq_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 embeddings_rabitq_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 embeddings_rabitq_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.
embeddings_rabitq_status 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.
This server
Across the catalogue