Retrieve creator fields.
AI agents call creator_fields to retrieve information from Mcp Zotero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about creator fields in a Zotero library without side effects. It is a read-only operation that queries bibliographic data. No data is created, modified, deleted, or executed. Blast radius is minimal — misuse by an agent would only expose bibliographic field schemas or creator information already in the user's library.
From the tool's definition Tool name is 'creator_fields' and description states 'Retrieve creator fields' — a pure query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Retrieve creator fields. It is categorised as a Read tool in the Mcp Zotero MCP Server, which means it retrieves data without modifying state.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for creator_fields: 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 Mcp Zotero. Nothing to install.
creator_fields 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 creator_fields 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 creator_fields. 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.
creator_fields is provided by the Mcp Zotero MCP server (nealcaren/mcp-zotero). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →