# 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.

Agent View of the PolicyLayer registry record for `embeddings_rabitq_status`. HTML page: https://policylayer.com/tools/ruflo/embeddings-rabitq-status

## Facts

- Tool: `embeddings_rabitq_status`
- Server: Ruflo (`ruvnet/ruflo`) — https://policylayer.com/tools/ruflo.md
- Homepage: https://github.com/ruvnet/ruflo
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "embeddings_rabitq_status",
    "arguments": {}
  }
}
```

## Why embeddings_rabitq_status is rated Low

This tool retrieves status and metadata about a vector embedding index (RaBitQ). It queries index properties like availability, vector count, and compression ratio with no side effects, no state modification, no code execution, and no data deletion.

From the tool's own definition: "Tool name 'embeddings_rabitq_status' and description 'Get RaBitQ quantized index status — availability, vector count, compression ratio' indicate retrieval of status information about an embedding index."

## Use case

AI agents call embeddings_rabitq_status to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Ruflo:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "embeddings_rabitq_status": {}
  }
}
```

## Other tools on Ruflo (495)

- `agent_terminate` — Destructive — https://policylayer.com/tools/ruflo/agent-terminate.md
- `agentdb_batch` — Destructive — https://policylayer.com/tools/ruflo/agentdb-batch.md
- `agentdb_causal-edge-delete` — Destructive — https://policylayer.com/tools/ruflo/agentdb-causal-edge-delete.md
- `agentdb_causal-node-delete` — Destructive — https://policylayer.com/tools/ruflo/agentdb-causal-node-delete.md
- `agentdb_hierarchical-delete` — Destructive — https://policylayer.com/tools/ruflo/agentdb-hierarchical-delete.md
- `autopilot_reset` — Destructive — https://policylayer.com/tools/ruflo/autopilot-reset.md
- `config_reset` — Destructive — https://policylayer.com/tools/ruflo/config-reset.md
- `federation_wg_keyrotate` — Destructive — https://policylayer.com/tools/ruflo/federation-wg-keyrotate.md
- `hooks_intelligence-reset` — Destructive — https://policylayer.com/tools/ruflo/hooks-intelligence-reset.md
- `hooks_worker-cancel` — Destructive — https://policylayer.com/tools/ruflo/hooks-worker-cancel.md
- `iot_device_remove` — Destructive — https://policylayer.com/tools/ruflo/iot-device-remove.md
- `iot_device_unpair` — Destructive — https://policylayer.com/tools/ruflo/iot-device-unpair.md
- `iot_firmware_rollout_rollback` — Destructive — https://policylayer.com/tools/ruflo/iot-firmware-rollout-rollback.md
- `iot_fleet_delete` — Destructive — https://policylayer.com/tools/ruflo/iot-fleet-delete.md
- `iot_fleet_remove_device` — Destructive — https://policylayer.com/tools/ruflo/iot-fleet-remove-device.md
- `managed_agent_terminate` — Destructive — https://policylayer.com/tools/ruflo/managed-agent-terminate.md
- `memory_delete` — Destructive — https://policylayer.com/tools/ruflo/memory-delete.md
- `policy_revoke` — Destructive — https://policylayer.com/tools/ruflo/policy-revoke.md
- `ruvector_delete` — Destructive — https://policylayer.com/tools/ruflo/ruvector-delete.md
- `session_delete` — Destructive — https://policylayer.com/tools/ruflo/session-delete.md
- `system_reset` — Destructive — https://policylayer.com/tools/ruflo/system-reset.md
- `task_cancel` — Destructive — https://policylayer.com/tools/ruflo/task-cancel.md
- `wasm_agent_reset` — Destructive — https://policylayer.com/tools/ruflo/wasm-agent-reset.md
- `wasm_gallery_remove_custom` — Destructive — https://policylayer.com/tools/ruflo/wasm-gallery-remove-custom.md
- `workflow_cancel` — Destructive — https://policylayer.com/tools/ruflo/workflow-cancel.md
- `workflow_delete` — Destructive — https://policylayer.com/tools/ruflo/workflow-delete.md
- `agent_pool` — Execute — https://policylayer.com/tools/ruflo/agent-pool.md
- `agent_spawn` — Execute — https://policylayer.com/tools/ruflo/agent-spawn.md
- `agentdb_consolidate` — Execute — https://policylayer.com/tools/ruflo/agentdb-consolidate.md
- `agentdb_route` — Execute — https://policylayer.com/tools/ruflo/agentdb-route.md
- …and 465 more: https://policylayer.com/tools/ruflo.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ruflo · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ruflo