Save a paper by URL (arXiv/CVF/rxiv), attach PDF/metadata
AI agents use save_paper_to_zotero to create or update resources in ZotLink — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZotLink environment.
This tool creates new entries in a user's Zotero library and attaches files—classic Write operations. The data is stored in the user's personal bibliography system and can be deleted or modified later, making it reversible. There is no deletion, code execution, or financial impact.
From the tool's definition Tool name 'save_paper_to_zotero' and description 'Save a paper by URL... attach PDF/metadata' indicate creation/modification of bibliography data in Zotero. The verb 'save' combined with 'attach' shows reversible data creation operations.
Documented attack patterns abuse exactly the kind of access save_paper_to_zotero gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZotLink, and nothing reaches the server without passing your rules. This is the rule we recommend for save_paper_to_zotero:
{
"version": "1",
"default": "deny",
"tools": {
"save_paper_to_zotero": {
"limits": [
{
"counter": "save_paper_to_zotero_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_paper_to_zotero 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.
Save a paper by URL (arXiv/CVF/rxiv), attach PDF/metadata. It is categorised as a Write tool in the ZotLink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZotLink MCP server in PolicyLayer and add a rule for save_paper_to_zotero: 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 ZotLink. Nothing to install.
save_paper_to_zotero 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 save_paper_to_zotero 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 save_paper_to_zotero. 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.
save_paper_to_zotero is provided by the ZotLink MCP server (tonybotni/zotlink). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 ZotLink tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 ZotLink tools catalogued and risk-classified — across an index of 42,500+ MCP servers.