AI agents use pinecone_upsert_vectors to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Pinecone API key |
vectors | array | Yes | Array of {id, values, metadata?} objects to upsert |
namespace | string | — | Namespace to write to |
index_host | string | Yes | Index host URL from describe_index |
Parameters from the server's own tool schema.
Upsert is a reversible write operation that creates or modifies data in a vector store. While it modifies state, it is not destructive (data can be updated again or deleted separately) and does not execute arbitrary code or move funds. The medium severity reflects the risk of corrupting vector embeddings or poisoning a vector index if an AI agent misuses this tool with malicious or incorrect vector data.
From the tool's definition Tool name 'pinecone_upsert_vectors' and description 'Upsert (insert or update) vectors into a Pinecone index' explicitly performs data modification operations (insert or update) on a Pinecone vector database index.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Upsert (insert or update) vectors into a Pinecone index. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pinecone_upsert_vectors accepts 4 parameters: api_key, vectors, namespace, index_host. Required: api_key, vectors, 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_upsert_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_upsert_vectors 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 pinecone_upsert_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_upsert_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_upsert_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →