sync_zotero_local
A write tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/sync-zotero-local.md
What sync_zotero_local does on Metis Public Health
AI agents use sync_zotero_local to create or update resources in Metis Public Health, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.
Why sync_zotero_local is rated Medium
The name implies a sync operation with a local Zotero reference manager, which typically involves reading from Zotero and writing/updating the local index. Sync operations generally fall under Write as they create or modify data reversibly. However, confidence is low due to the empty description — the tool could also involve destructive overwrites or purely read operations.
From the tool's definition Tool name 'sync_zotero_local' suggests synchronizing data with a local Zotero library. The description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs sync_zotero_local safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_zotero_local, this is the rule to start with:
sync_zotero_local stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every sync_zotero_local call is checked against it from then on.
Questions about sync_zotero_local
sync_zotero_local is a write tool on the Metis Public Health MCP server. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for sync_zotero_local: 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 Metis Public Health. Nothing to install.
sync_zotero_local 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 sync_zotero_local 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 sync_zotero_local. 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.
sync_zotero_local is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue