pinecone_list_indexes
List all Pinecone vector indexes in the project.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pinecone-list-indexes.md
What pinecone_list_indexes does on UnClick
AI agents call pinecone_list_indexes to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Pinecone API key from app.pinecone.io |
Parameters from the server's own tool schema.
Why pinecone_list_indexes is rated Low
This tool queries and retrieves metadata about existing Pinecone indexes without modifying, deleting, or executing operations on them. It is a straightforward read operation with minimal blast radius if misused by an AI agent, as it only exposes information about the project's vector indexes.
From the tool's definition Tool name contains 'list' and description states 'List all Pinecone vector indexes' — retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pinecone_list_indexes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pinecone_list_indexes, this is the rule to start with:
pinecone_list_indexes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every pinecone_list_indexes call is checked against it from then on.
Questions about pinecone_list_indexes
List all Pinecone vector indexes in the project. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pinecone_list_indexes accepts 1 parameter: api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pinecone_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 UnClick. Nothing to install.
pinecone_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 pinecone_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 pinecone_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.
pinecone_list_indexes is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue