zotero_search_by_tag

A read tool on the Zotero MCP server.

SERVERZotero MCP SOURCEpypi:zotero-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-zotero-mcp/zotero-search-by-tag.md

WHAT IT DOES

What zotero_search_by_tag does on Zotero MCP

AI agents call zotero_search_by_tag to retrieve information from Zotero MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zotero_search_by_tag is rated Low

Searching a research library by tag is a read-only query operation that retrieves information without side effects. The tool filters existing data in the Zotero library. Even though the description is empty, the tool name and the pattern of sibling tools (search, fetch for reads; zotero_add_* for writes) make it clear this performs retrieval only.

From the tool's definition Tool name 'zotero_search_by_tag' indicates a search operation. Sibling tools include 'search' and 'fetch' which are explicitly Read operations. No description provided, but naming convention and context strongly suggest data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zotero_search_by_tag safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zotero MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zotero_search_by_tag, this is the rule to start with:

zotero_search_by_tag Allowed

zotero_search_by_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zotero_search_by_tag": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zotero MCP, apply this rule, and every zotero_search_by_tag call is checked against it from then on.

FAQ

Questions about zotero_search_by_tag

What does the zotero_search_by_tag tool do? +

zotero_search_by_tag is a read tool on the Zotero MCP server. It is categorised as a Read tool in the Zotero MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zotero_search_by_tag? +

Register the Zotero MCP server in PolicyLayer and add a rule for zotero_search_by_tag: 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 MCP. Nothing to install.

What risk level is zotero_search_by_tag? +

zotero_search_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zotero_search_by_tag? +

Yes. Add a rate_limit block to the zotero_search_by_tag 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.

How do I block zotero_search_by_tag completely? +

Set action: deny in the PolicyLayer policy for zotero_search_by_tag. 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.

What MCP server provides zotero_search_by_tag? +

zotero_search_by_tag is provided by the Zotero MCP server (pypi:zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zotero, and thousands of servers like it.

This server

All 55 Zotero tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →