AI agents call list-indexes 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 retrieves metadata about Pinecone indexes without creating, modifying, deleting, or executing any operations. It is a simple informational query with minimal blast radius—exposing the names of available indexes presents only an information disclosure risk, not a data manipulation or destructive risk.
From the tool's definition Tool name 'list-indexes' and description 'Lists all Pinecone indexes' indicate a retrieval operation with no side effects. The verb 'lists' is a classic Read operation that queries and returns data about existing indexes without modification.
Documented attack patterns abuse exactly the kind of access list-indexes 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 list-indexes:
{
"version": "1",
"default": "deny",
"tools": {
"list-indexes": {}
}
}list-indexes 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.
Lists all Pinecone indexes. 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 list-indexes: 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.
list-indexes 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 list-indexes 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 list-indexes. 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.
list-indexes 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.