sync_zotero_local · Metis Public Health MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why sync_zotero_local needs a policy

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

Recommended rule Ready

Verdict

sync_zotero_local Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_zotero_local": {
      "limits": [
        {
          "counter": "sync_zotero_local_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metis Public Health, so you can run agents against it safely.

FAQ

Questions about sync_zotero_local

What does the sync_zotero_local tool do? +

sync_zotero_local. 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.

How do I enforce a policy on sync_zotero_local? +

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.

What risk level is sync_zotero_local? +

sync_zotero_local is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_zotero_local? +

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.

How do I block sync_zotero_local completely? +

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.

What MCP server provides sync_zotero_local? +

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.