get_citation_edges
[MAINTENANCE] fefb596a — read the CITATION GRAPH of a project's ingested documents. Returns every in-text citation marker (a kind='citation' element parsed from an ingested .tex/.docx) together with its resolved edges: • bibentry edges — the intra-document link from a \cite{key} marker to a match...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-citation-edges.md
What get_citation_edges does on Meridian
AI agents call get_citation_edges to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Restrict to the document stored under this source (path/URL). Empty graph if the source is unknown. |
project_id | string | — | |
document_id | string | — | Restrict to one stored document by its doc_store id. |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. |
Parameters from the server's own tool schema.
Why get_citation_edges is rated Low
This tool retrieves and queries existing citation graph data from ingested documents. It performs no writes, deletes, executions, or financial operations. The blast radius of misuse is minimal—an agent could only read citation metadata that has already been ingested, potentially exposing document structure or bibliography information, but cannot modify or delete anything.
From the tool's definition Tool description explicitly states 'read the CITATION GRAPH' and 'Returns every in-text citation marker...together with its resolved edges'.
Attacks that exploit this kind of access
The rule that runs get_citation_edges 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 get_citation_edges, this is the rule to start with:
get_citation_edges is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_citation_edges call is checked against it from then on.
Questions about get_citation_edges
[MAINTENANCE] fefb596a — read the CITATION GRAPH of a project's ingested documents. Returns every in-text citation marker (a kind='citation' element parsed from an ingested .tex/.docx) together with its resolved edges: • bibentry edges — the intra-document link from a \cite{key} marker to a matching \bibitem/bibliography entry in the SAME document (materialised automatically on ingest). • zotero_item edges — the cross-document link from a marker to a canonical Zotero library item, keyed on DOI (materialised by the opt-in resolve_citations pass); target_document_id is set when the cited paper is itself ingested in this project. Each marker carries {element_id, document_id, ordinal, ref, text, edges:[{edge_kind, target_kind, target_ref, target_element_id, target_document_id, resolved_at}]}. Scope to one document with source (a stored source path/URL) or document_id; omit both for the whole project. Returns an empty markers list (never an error) when no document structure has been persisted yet. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_citation_edges accepts 4 parameters: source, project_id, document_id, project_name. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_citation_edges: 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.
get_citation_edges is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_citation_edges 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 get_citation_edges. 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.
get_citation_edges 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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue