pinecone_describe_index
Get details (dimension, metric, status, host) for a Pinecone index.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pinecone-describe-index.md
What pinecone_describe_index does on UnClick
AI agents call pinecone_describe_index 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 |
index_name | string | Yes | Index name |
Parameters from the server's own tool schema.
Why pinecone_describe_index is rated Low
This tool queries and retrieves information about a Pinecone vector database index. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. It is a straightforward metadata retrieval operation, making it a Read category tool with low severity since misuse would only expose database configuration details.
From the tool's definition Tool performs 'Get details' operation on a Pinecone index, retrieving read-only metadata (dimension, metric, status, host) without modification or execution.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pinecone_describe_index 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_describe_index, this is the rule to start with:
pinecone_describe_index 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_describe_index call is checked against it from then on.
Questions about pinecone_describe_index
Get details (dimension, metric, status, host) for a Pinecone index. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pinecone_describe_index accepts 2 parameters: api_key, index_name. Required: api_key, index_name. 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_describe_index: 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_describe_index 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_describe_index 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_describe_index. 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_describe_index 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