Inserts or updates records in an index with integrated inference.
AI agents use upsert-records to create or update resources in Pinecone Developer MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pinecone Developer MCP environment.
The tool performs create and update operations on data in a vector index. While these are reversible modifications, they can affect stored data at scale. Classified as Write rather than Execute because the operation is data modification rather than code execution, and it's reversible unlike Destructive operations.
From the tool's definition 'Inserts or updates records' - tool modifies data by creating new records or updating existing ones in a Pinecone index. This is reversible (records can be updated again or deleted via other tools).
Documented attack patterns abuse exactly the kind of access upsert-records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pinecone Developer MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for upsert-records:
{
"version": "1",
"default": "deny",
"tools": {
"upsert-records": {
"limits": [
{
"counter": "upsert-records_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upsert-records stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inserts or updates records in an index with integrated inference. It is categorised as a Write tool in the Pinecone Developer MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pinecone Developer MCP server in PolicyLayer and add a rule for upsert-records: 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 Pinecone Developer MCP. Nothing to install.
upsert-records 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 upsert-records 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 upsert-records. 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.
upsert-records is provided by the Pinecone Developer MCP server (pinecone-io/pinecone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Pinecone Developer MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Pinecone Developer MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.