pinecone_delete_vectors
Delete vectors from a Pinecone index by ID or filter.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pinecone-delete-vectors.md
What pinecone_delete_vectors does on UnClick
AI agents call pinecone_delete_vectors to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | array | — | Array of vector IDs to delete |
filter | object | — | Metadata filter - delete matching vectors |
api_key | string | Yes | Pinecone API key |
namespace | string | — | Namespace to delete from |
delete_all | boolean | — | Delete all vectors in the namespace |
index_host | string | Yes | Index host URL from describe_index |
Parameters from the server's own tool schema.
Why pinecone_delete_vectors is rated Critical
The tool irreversibly deletes vector embeddings from a Pinecone index. Deletion of indexed data cannot be undone without restoration from backups. This is a destructive operation with potential for significant data loss if misused by an AI agent (e.g., deleting critical embeddings used for retrieval-augmented generation or similarity search).
From the tool's definition Tool name 'pinecone_delete_vectors' and description 'Delete vectors from a Pinecone index by ID or filter' explicitly perform deletion operations on stored data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pinecone_delete_vectors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pinecone_delete_vectors, this is the rule to start with:
pinecone_delete_vectors 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 UnClick, apply this rule, and every pinecone_delete_vectors call is checked against it from then on.
Questions about pinecone_delete_vectors
Delete vectors from a Pinecone index by ID or filter. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
pinecone_delete_vectors accepts 6 parameters: ids, filter, api_key, namespace, delete_all, index_host. Required: api_key, index_host. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pinecone_delete_vectors: 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 UnClick. Nothing to install.
pinecone_delete_vectors 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 pinecone_delete_vectors 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 pinecone_delete_vectors. 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.
pinecone_delete_vectors is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue