get_document
AI agents call get_document to retrieve information from MCP Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves documents on demand without modifying, deleting, or executing anything. The empty description is supplemented by clear context from the server purpose (documentation delivery) and sibling tools (list_documents, search_in_document) which are all read operations. The security features mentioned in the server description imply this is a controlled retrieval mechanism with no side effects.
From the tool's definition Tool name 'get_document' combined with server description stating it 'Efficiently delivers project documentation' and supports 'document retrieval' indicates a read-only data retrieval operation.
Attacks that exploit this kind of access
get_document. It is categorised as a Read tool in the MCP Document Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Server 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 MCP Document Server. 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 MCP Document Server MCP server (onoda4480/document-server-mcp). 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 →