This record as markdown: /tools/ruflo/ruvector-delete.md
What ruvector_delete does on Ruflo
AI agents call ruvector_delete to permanently remove resources in Ruflo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why ruvector_delete is rated Critical
The tool performs an irreversible deletion of vectors identified by ID. In a vector database or RAG system (mentioned in server description), vectors often represent embeddings of documents or knowledge critical to agent function. Deletion cannot be undone and has blast radius across retrieval-augmented generation pipelines.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete vectors by ID' — this is an irreversible destruction operation on stored vector data.
Attacks that exploit this kind of access
The rule that runs ruvector_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, 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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every ruvector_delete call is checked against it from then on.
Questions about ruvector_delete
Delete vectors by ID. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ruflo 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 Ruflo. Nothing to install.
ruvector_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
ruvector_delete is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue