resolve_citations

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/resolve-citations.md

WHAT IT DOES

What resolve_citations does on Meridian

AI agents use resolve_citations to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.

Parameter	Type	Required	Description
`max_items`	integer	—	Cap how many unresolved markers to attempt this pass. Omit to attempt all.
`project_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally.

Parameters from the server's own tool schema.

RISK

Why resolve_citations is rated Medium

The tool performs persistent data modifications by creating and storing citation-to-Zotero-item relationships ('edges'). This qualifies as Write rather than Read because it creates new structured data relationships in the project. It is not Destructive because edge creation is reversible.

From the tool's definition resolve_citations materialises cross-document 'cites' -> zotero_item edges and creates links between citation markers and Zotero items. It modifies the project's citation graph by adding edges/relationships, which are persistent data modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resolve_citations safely

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

resolve_citations Rate-limited

resolve_citations 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": {
    "resolve_citations": {
      "limits": [
        {
          "counter": "resolve_citations_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about resolve_citations

What does the resolve_citations tool do? +

[MAINTENANCE] fefb596a — resolve this project's in-text citation markers to canonical Zotero items via Zotero's LOCAL API and materialise the cross-document 'cites' -> zotero_item edges (keyed on DOI). An OPT-IN, network-making pass — deliberately separate from ingest, which stays offline. For each kind='citation' marker without a zotero_item edge, the marker's ref is resolved: a DOI (doi:.. / a bare 10.x/y / a doi.org URL) matches the library item with that DOI; a zotero:<key> ref is a direct item lookup; a bare BibTeX citekey is a best-effort text search (fuzzy without Better BibTeX). When the resolved DOI matches a paper ALSO ingested in this project, the edge's target_document_id is linked too. IDEMPOTENT — re-runs only fill gaps, never duplicate. If Zotero is closed or its local API is disabled, markers simply stay unresolved (no error). Returns {resolved, unresolved, cross_doc_linked} counts. Requires Zotero running locally with the local API enabled (endpoint configurable via MERIDIAN_ZOTERO_API_URL). Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does resolve_citations accept? +

resolve_citations accepts 3 parameters: max_items, project_id, project_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_citations? +

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

What risk level is resolve_citations? +

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

Can I rate-limit resolve_citations? +

Yes. Add a rate_limit block to the resolve_citations 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 resolve_citations completely? +

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

resolve_citations is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →