Searches for records in an index based on a text query, using integrated inference for embedding. Has options for metadata filtering and reranking.
AI agents call search-records to retrieve information from Pinecone Developer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries data from a Pinecone index and returns results. There is no indication it modifies, creates, deletes, or executes code. The filtering and reranking options are applied to the query results, not to the underlying data. This is a classic Read operation with minimal risk if misused by an AI agent—the worst outcome is exposure of indexed records already accessible through search.
From the tool's definition Tool description states it "Searches for records in an index based on a text query" with "options for metadata filtering and reranking." The verb "searches" and lack of any modification/creation/deletion language indicate a read-only operation that retrieves…
Documented attack patterns abuse exactly the kind of access search-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 search-records:
{
"version": "1",
"default": "deny",
"tools": {
"search-records": {}
}
}search-records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Searches for records in an index based on a text query, using integrated inference for embedding. Has options for metadata filtering and reranking. It is categorised as a Read tool in the Pinecone Developer MCP MCP Server, which means it retrieves data without modifying state.
Register the Pinecone Developer MCP server in PolicyLayer and add a rule for search-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.
search-records is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search-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 search-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.
search-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.