Perform bulk operations on multiple correspondents: set permissions to control who can assign them to documents, or permanently delete multiple correspondents. Use with caution as deletion affects all associated documents.
AI agents call bulk_edit_correspondents to permanently remove resources in Paperless-NGX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool also supports reversible write operations (setting permissions), it includes a destructive capability to permanently delete correspondents and their associations. Per the classification rules, when a tool spans multiple categories, the most severe applies. Permanent deletion of data is irreversible and cannot be undone, placing this squarely in the Destructive category.
From the tool's definition The tool description explicitly states it can "permanently delete multiple correspondents" and warns "deletion affects all associated documents." The word "permanently" indicates irreversible data loss.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Perform bulk operations on multiple correspondents: set permissions to control who can assign them to documents, or permanently delete multiple correspondents. Use with caution as deletion affects all associated documents. It is categorised as a Destructive tool in the Paperless-NGX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Paperless-NGX MCP Server MCP server in PolicyLayer and add a rule for bulk_edit_correspondents: 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.
bulk_edit_correspondents is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bulk_edit_correspondents 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 bulk_edit_correspondents. 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.
bulk_edit_correspondents is provided by the Paperless-NGX MCP Server MCP server (mephistojb/paperless-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 →