Retrieve saved searches.
AI agents call list_searches 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 information about saved searches from a Zotero library. The verb 'Retrieve' and the action of listing/reading data with no side effects places it squarely in the Read category. There is no data creation, modification, deletion, or external operation triggering. The risk is minimal since querying saved searches poses no security or data integrity threat.
From the tool's definition Tool name 'list_searches' and description 'Retrieve saved searches' indicate a query operation that reads existing data without modification.
Attacks that exploit this kind of access
Retrieve saved searches. 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 list_searches: 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.
list_searches 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 list_searches 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 list_searches. 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.
list_searches 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 →