Create a new correspondent (person, company, or organization) for tracking document senders and receivers. Can include automatic matching patterns for smart assignment to incoming documents.
AI agents use create_correspondent to create or update resources in Paperless-NGX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paperless-NGX MCP Server environment.
The tool creates new metadata (a correspondent entity) in the Paperless-NGX system. This is a Write operation because it adds data without irreversible destruction. The severity is low because creating a correspondent has minimal blast radius—it only adds a new organizational entity for document categorization with no direct impact on document content or financial operations.
From the tool's definition Tool description explicitly states 'Create a new correspondent' which creates a new entity in the system. This is a reversible creation operation as evidenced by the sibling tool 'delete_tag' and bulk edit tools that indicate data can be modified.
Documented attack patterns abuse exactly the kind of access create_correspondent 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 create_correspondent:
{
"version": "1",
"default": "deny",
"tools": {
"create_correspondent": {
"limits": [
{
"counter": "create_correspondent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_correspondent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new correspondent (person, company, or organization) for tracking document senders and receivers. Can include automatic matching patterns for smart assignment to incoming documents. It is categorised as a Write tool in the Paperless-NGX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paperless-NGX MCP Server MCP server in PolicyLayer and add a rule for create_correspondent: 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.
create_correspondent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_correspondent 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 create_correspondent. 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.
create_correspondent 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.
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.