Get annotations and notes for specific items with color/tag filtering. REQUIRED: provide one of itemKey, annotationId, or annotationIds (use search_library first to find the itemKey; use search_annotations to search by colors/tags across the library). Returns user\
AI agents call get_annotations to retrieve information from Zotero Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries annotations and notes associated with Zotero items. It performs a lookup operation with filtering capabilities (color/tag) but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only access existing annotations it already has keys for. No data is changed, no code is executed, and no irreversible actions are possible.
From the tool's definition Tool description states 'Get annotations and notes for specific items' — a retrieval operation with no modification or side effects. The parameters (itemKey, annotationId, annotationIds) are for querying existing data, and the return value is read-only data.
Attacks that exploit this kind of access
Get annotations and notes for specific items with color/tag filtering. REQUIRED: provide one of itemKey, annotationId, or annotationIds (use search_library first to find the itemKey; use search_annotations to search by colors/tags across the library). Returns user\. It is categorised as a Read tool in the Zotero Agent MCP Server, which means it retrieves data without modifying state.
Register the Zotero Agent MCP server in PolicyLayer and add a rule for get_annotations: 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 Agent. Nothing to install.
get_annotations 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_annotations 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_annotations. 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_annotations is provided by the Zotero Agent MCP server (psiQAQ/zotero-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_annotations is one line of Zotero Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →