Retrieve the content of a specific document by path. Supports pagination to avoid overwhelming responses.
AI agents call get_document to retrieve information from Embeddings Searcher without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns document content without creating, modifying, deleting, or executing anything. It is a straightforward read operation that queries documentation from a repository. No side effects, no state changes, no code execution. Pagination is a standard UX feature for large documents.
From the tool's definition Tool description states 'Retrieve the content of a specific document by path' with pagination support. The verb 'retrieve' and the operation of reading document content without modification are characteristic of Read operations.
Attacks that exploit this kind of access
Retrieve the content of a specific document by path. Supports pagination to avoid overwhelming responses. It is categorised as a Read tool in the Embeddings Searcher MCP Server, which means it retrieves data without modifying state.
Register the Embeddings Searcher MCP server in PolicyLayer and add a rule for get_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 Embeddings Searcher. Nothing to install.
get_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 get_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 get_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.
get_document is provided by the Embeddings Searcher MCP server (thypon/kb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →