mendeley_add_document
AI agents use mendeley_add_document to create or update resources in Mendeley — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mendeley environment.
This tool creates or adds a new document to the user's academic reference library. This is a Write operation because it creates data reversibly (documents can be removed or modified later). The severity is medium because misuse could pollute or disorganize a user's academic library, but the impact is limited in scope and reversible.
From the tool's definition Tool name 'mendeley_add_document' indicates creation/addition of a document to the Mendeley library. The server description confirms it 'manage[s] your academic library', and 'add' is a reversible write operation.
Documented attack patterns abuse exactly the kind of access mendeley_add_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mendeley, and nothing reaches the server without passing your rules. This is the rule we recommend for mendeley_add_document:
{
"version": "1",
"default": "deny",
"tools": {
"mendeley_add_document": {
"limits": [
{
"counter": "mendeley_add_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mendeley_add_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.
mendeley_add_document. It is categorised as a Write tool in the Mendeley MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mendeley MCP server in PolicyLayer and add a rule for mendeley_add_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 Mendeley. Nothing to install.
mendeley_add_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 mendeley_add_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 mendeley_add_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.
mendeley_add_document is provided by the Mendeley MCP server (pallaprolus/mendeley-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mendeley, 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 Mendeley tools catalogued and risk-classified — across an index of 43,000+ MCP servers.