ruvector_delete

Delete vectors by ID.

SERVERClaude Flow SOURCEclaude-flow

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/ruvector-delete.md

WHAT IT DOES

What ruvector_delete does on Claude Flow

AI agents call ruvector_delete to permanently remove resources in Claude Flow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why ruvector_delete is rated Critical

The tool performs deletion of data (vectors) by identifier. Deletion is irreversible and cannot be undone, placing it in the Destructive category. Severity is high because bulk or mistaken vector deletion could corrupt AI model state, embeddings, or search indices in an enterprise system, though the impact is typically recoverable via backups rather than catastrophic system-wide failure (hence not critical).

From the tool's definition Tool name includes 'delete' and description states 'Delete vectors by ID' — this is an irreversible deletion operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ruvector_delete 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 ruvector_delete, this is the rule to start with:

ruvector_delete Hidden

ruvector_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "ruvector_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every ruvector_delete call is checked against it from then on.

FAQ

Questions about ruvector_delete

What does the ruvector_delete tool do? +

Delete vectors by ID. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ruvector_delete? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for ruvector_delete: 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.

What risk level is ruvector_delete? +

ruvector_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ruvector_delete? +

Yes. Add a rate_limit block to the ruvector_delete 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.

How do I block ruvector_delete completely? +

Set action: deny in the PolicyLayer policy for ruvector_delete. 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.

What MCP server provides ruvector_delete? +

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

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →