Delete a vector store
AI agents call vector-store-delete to permanently remove resources in Universal OpenAI Vector Store MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This operation permanently deletes a vector store, which cannot be undone. The deletion of an entire data store is a destructive action with significant blast radius—loss of all indexed documents and embeddings. While not financial in nature, it represents irreversible data destruction, making it more severe than Write or Execute operations.
From the tool's definition The tool is named 'vector-store-delete' with description 'Delete a vector store', indicating irreversible removal of an entire vector database and its contents.
Documented attack patterns abuse exactly the kind of access vector-store-delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Universal OpenAI Vector Store MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for vector-store-delete:
{
"version": "1",
"default": "deny",
"hide": [
"vector-store-delete"
]
} vector-store-delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a vector store. It is categorised as a Destructive tool in the Universal OpenAI Vector Store MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Universal OpenAI Vector Store MCP Server MCP server in PolicyLayer and add a rule for vector-store-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 Universal OpenAI Vector Store MCP Server. Nothing to install.
vector-store-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 vector-store-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 vector-store-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.
vector-store-delete is provided by the Universal OpenAI Vector Store MCP Server MCP server (jezweb/openai-vector-assistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Universal OpenAI Vector Store MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Universal OpenAI Vector Store MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.