Get stats about the Pinecone index, including the number of records, dimensions, and namespaces.
AI agents call pinecone-stats to retrieve information from Mcp Pinecone without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports metadata and statistics about an existing index. It does not create, modify, delete, or execute operations on data. The blast radius of misuse is minimal — an agent gaining access would only be able to inspect index properties, not alter them or access sensitive data beyond what the stats reveal.
From the tool's definition Tool retrieves stats about the Pinecone index including 'number of records, dimensions, and namespaces' — purely query/reporting operations with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access pinecone-stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Pinecone, and nothing reaches the server without passing your rules. This is the rule we recommend for pinecone-stats:
{
"version": "1",
"default": "deny",
"tools": {
"pinecone-stats": {}
}
}pinecone-stats 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.
Get stats about the Pinecone index, including the number of records, dimensions, and namespaces. It is categorised as a Read tool in the Mcp Pinecone MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pinecone MCP server in PolicyLayer and add a rule for pinecone-stats: 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 Mcp Pinecone. Nothing to install.
pinecone-stats 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 pinecone-stats 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-stats. 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-stats is provided by the Mcp Pinecone MCP server (sirmews/mcp-pinecone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Mcp Pinecone tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Mcp Pinecone tools catalogued and risk-classified — across an index of 42,500+ MCP servers.