List all correspondents or create a new correspondent in Paperless-ngx
AI agents use crow_paperless_correspondents to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
The tool performs both retrieval ('List all correspondents') and creation ('create a new correspondent') operations. Creation of new records is a reversible Write operation. While listing is Read-only, the presence of the create capability makes this a Write tool.
From the tool's definition Tool description states 'create a new correspondent in Paperless-ngx', which is a data modification operation. The listing capability is a Read operation, but the creation capability elevates this to Write category.
Documented attack patterns abuse exactly the kind of access crow_paperless_correspondents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_paperless_correspondents:
{
"version": "1",
"default": "deny",
"tools": {
"crow_paperless_correspondents": {
"limits": [
{
"counter": "crow_paperless_correspondents_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} crow_paperless_correspondents 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.
List all correspondents or create a new correspondent in Paperless-ngx. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_paperless_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 Crow. Nothing to install.
crow_paperless_correspondents 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 crow_paperless_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 crow_paperless_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.
crow_paperless_correspondents is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.