Get full-text content from PDFs, attachments, notes, and abstracts. May contain OCR artifacts. When user asks for complete text, provide it without summarization.
AI agents call get_content to retrieve information from Zotero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing content from Zotero without modifying, deleting, or executing any operations. It has no side effects beyond reading data. The mention of OCR artifacts and instruction to provide text without summarization confirms it is a pure read operation. Low severity because reading academic content poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states: 'Get full-text content from PDFs, attachments, notes, and abstracts.' The verb 'Get' and the retrieval-only nature (no modification, deletion, or execution) clearly indicate data retrieval.
Documented attack patterns abuse exactly the kind of access get_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zotero, and nothing reaches the server without passing your rules. This is the rule we recommend for get_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_content": {}
}
} get_content is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get full-text content from PDFs, attachments, notes, and abstracts. May contain OCR artifacts. When user asks for complete text, provide it without summarization. It is categorised as a Read tool in the Zotero MCP Server, which means it retrieves data without modifying state.
Register the Zotero MCP server in PolicyLayer and add a rule for get_content: 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 Zotero. Nothing to install.
get_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_content 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 get_content. 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.
get_content is provided by the Zotero MCP server (zotero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zotero, 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.
27 Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.