AI agents call read-document 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 retrieves data from a vector database index without side effects. It performs a query operation to fetch an existing document, which is characteristic of Read category tools. No data is created, modified, deleted, or executed. The low severity reflects the minimal risk of misuse—reading documents from a search index poses no blast radius beyond information disclosure.
From the tool's definition Tool name is 'read-document' and description states 'Read a document from the Pinecone index.' The verb 'read' and action of retrieving a document with no mention of modification, deletion, or execution clearly indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access read-document 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 read-document:
{
"version": "1",
"default": "deny",
"tools": {
"read-document": {}
}
}read-document 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.
Read a document from the Pinecone index. 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 read-document: 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.
read-document 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 read-document 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 read-document. 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.
read-document 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.