Reranks a collection of records or text documents using a specialized reranking model.
AI agents call rerank-documents 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.
Reranking is a computational transformation applied to existing data that produces no side effects, modifications to the underlying data, or external operations. The tool accepts documents as input, applies a ranking algorithm, and returns results—characteristic of a Read operation.
From the tool's definition The tool description states it 'reranks a collection of records or text documents using a specialized reranking model.' This is a read-only operation that takes existing documents as input and returns them in a different order based on relevance scoring.
Documented attack patterns abuse exactly the kind of access rerank-documents 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 rerank-documents:
{
"version": "1",
"default": "deny",
"tools": {
"rerank-documents": {}
}
} rerank-documents 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.
Reranks a collection of records or text documents using a specialized reranking model. 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 rerank-documents: 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.
rerank-documents 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 rerank-documents 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 rerank-documents. 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.
rerank-documents 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.