Create a vector index (HNSW or IVF) for faster similarity search.
AI agents use ruvector_create_index to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
This tool creates new persistent data structures (vector indexes using HNSW or IVF algorithms). Creation is a Write operation because it modifies the database/vector store state. Severity is medium because misconfiguration could degrade performance or consume resources, but the action is reversible through index deletion. No data is destroyed, no code is executed, and no financial impact occurs.
From the tool's definition Tool name 'create_index' and description 'Create a vector index' indicate irreversible creation of a new data structure.
Attacks that exploit this kind of access
Create a vector index (HNSW or IVF) for faster similarity search. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for ruvector_create_index: 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.
ruvector_create_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ruvector_create_index 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_create_index. 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_create_index 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.