Create a saved search.
AI agents use create_saved_search to create or update resources in Mcp Zotero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Zotero environment.
The tool creates a new saved search configuration in Zotero. This is a reversible, non-destructive operation (searches can be modified or deleted). It does not execute arbitrary code, delete data, move money, or retrieve existing data for external use. The blast radius of misuse is low—a malicious actor could create many searches, but this causes no data loss and has minimal operational impact.
From the tool's definition Tool name 'create_saved_search' and description 'Create a saved search' indicate creation of a saved search object, which is a reversible data modification operation in Zotero. This is consistent with the Write category (create, update, post, upload).
Attacks that exploit this kind of access
Create a saved search. It is categorised as a Write tool in the Mcp Zotero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for create_saved_search: 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.
create_saved_search 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 create_saved_search 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 create_saved_search. 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.
create_saved_search 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 →