AI agents use reader_create_document to create or update resources in Reader MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reader MCP Server environment.
The tool creates new documents in the Readwise Reader library, which is a reversible operation (documents can be updated or deleted by other tools on the server). This fits the Write category. Severity is medium because uncontrolled document creation could clutter the knowledge repository or create false/misleading entries, but the impact is limited to the user's own knowledge base.
From the tool's definition Tool name 'reader_create_document' indicates creation of data. Server description confirms the tool operates on a 'personal knowledge repository' and the sibling tools include 'reader_update_document' and 'reader_delete_document', establishing that this…
Documented attack patterns abuse exactly the kind of access reader_create_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reader MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reader_create_document:
{
"version": "1",
"default": "deny",
"tools": {
"reader_create_document": {
"limits": [
{
"counter": "reader_create_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reader_create_document 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.
reader_create_document. It is categorised as a Write tool in the Reader MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reader MCP Server MCP server in PolicyLayer and add a rule for reader_create_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 Reader MCP Server. Nothing to install.
reader_create_document 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 reader_create_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.
Set action: deny in the PolicyLayer policy for reader_create_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.
reader_create_document is provided by the Reader MCP Server MCP server (xinthink/reader-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reader MCP Server, 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.
7 Reader MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.