check_paperless
Check Paperless-NGX document management health. Attempts GET /api/ (returns 401 without auth, confirming service is running). Returns reachable state.
This record as markdown: /tools/aaronckj-mcp-nettools/check-paperless.md
What check_paperless does on Mcp Nettools
AI agents call check_paperless to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_paperless is rated Low
This is a health check tool that queries the Paperless-NGX service to confirm it is running and reachable. It performs a GET request which is idempotent and has no side effects beyond retrieving state information. The expected 401 response without credentials confirms the tool is simply probing service availability, not accessing sensitive document data or performing any modifications.
From the tool's definition Tool performs a GET request to /api/ endpoint to check service reachability and health status. Returns 401 without authentication, indicating read-only probe of service state. No data modification, code execution, or destructive operations.
Attacks that exploit this kind of access
The rule that runs check_paperless safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_paperless, this is the rule to start with:
check_paperless 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 Mcp Nettools, apply this rule, and every check_paperless call is checked against it from then on.
Questions about check_paperless
Check Paperless-NGX document management health. Attempts GET /api/ (returns 401 without auth, confirming service is running). Returns reachable state. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_paperless: 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 Nettools. Nothing to install.
check_paperless 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 check_paperless 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 check_paperless. 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.
check_paperless is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue