Low Risk

get_document

Get complete details for a specific document including full metadata, content preview, tags, correspondent, and document type information.

How to control get_document ↓

AI agents call get_document to retrieve information from Paperless-NGX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves and queries document information without creating, modifying, deleting, or executing any external actions. It is purely informational and has no side effects on the Paperless-NGX system. Severity is low because exposure of this tool allows an AI agent to read potentially sensitive document metadata, but cannot cause irreversible harm or unauthorized modifications.

From the tool's definition Tool name is 'get_document' and description states it 'Get[s] complete details for a specific document including full metadata, content preview, tags, correspondent, and document type information.' This is a retrieval operation with no modification or…

Documented attack patterns abuse exactly the kind of access get_document gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Paperless-NGX MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document": {}
  }
}

get_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Paperless-NGX MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_document tool do? +

Get complete details for a specific document including full metadata, content preview, tags, correspondent, and document type information. It is categorised as a Read tool in the Paperless-NGX MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document? +

Register the Paperless-NGX MCP 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 Paperless-NGX MCP Server. Nothing to install.

What risk level is get_document? +

get_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_document? +

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.

How do I block get_document completely? +

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.

What MCP server provides get_document? +

get_document is provided by the Paperless-NGX MCP Server MCP server (nloui/paperless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Paperless-NGX MCP Server tool call.

Deterministic rules across all 16 Paperless-NGX MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 Paperless-NGX MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.