ingest_document_structure

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 62 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/ingest-document-structure.md

WHAT IT DOES

What ingest_document_structure does on Meridian

AI agents use ingest_document_structure 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
`title`	string	—	Document title (optional; stored for display).
`blocks`	string	Yes	JSON-encoded list of body blocks from document_content_tree (the 'blocks' key) — headings, paragraphs, tables in document order. The server converts these to st
`source`	string	Yes	The source key (usually the local file path) matching what ingest_document stored the flat note under.
`doc_type`	string	—	Document type: 'docx' (default) or 'latex'.
`project_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.

Parameters from the server's own tool schema.

RISK

Why ingest_document_structure is rated Medium

This tool writes/persists structured document data into a store. It creates or modifies data in a reversible way (data can be overwritten or updated). It does not execute code, delete data, or involve financial transactions. The severity is medium because misuse could corrupt the document index or cause mismatches in document_id lookups, affecting downstream tools like find_similar_figure and index_table.

From the tool's definition persist pre-parsed structural data (headings/figures/tables) into the doc-structure store

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ingest_document_structure 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 ingest_document_structure, this is the rule to start with:

ingest_document_structure Rate-limited

ingest_document_structure 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": {
    "ingest_document_structure": {
      "limits": [
        {
          "counter": "ingest_document_structure_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 ingest_document_structure call is checked against it from then on.

FAQ

Questions about ingest_document_structure

What does the ingest_document_structure tool do? +

[MAINTENANCE] db42acce — persist pre-parsed structural data (headings/figures/tables) into the doc-structure store, keyed on the SAME source as ingest_document(content=...) so find_similar_figure / index_figure / index_table / index_equation see the correct document_id. Use this when the .docx lives on the caller's local machine (not on the Meridian server): call the tunnel-side ingest_local_document_structure tool (from the meridian-docs extension) which parses the file locally and forwards the blocks JSON here. The source must exactly match the source that ingest_document stored the flat note under (default: the local file path). Returns {document_id, source, doc_type, element_count}. 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 ingest_document_structure accept? +

ingest_document_structure accepts 6 parameters: title, blocks, source, doc_type, project_id, project_name. Required: blocks, source. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ingest_document_structure? +

Register the Meridian MCP server in PolicyLayer and add a rule for ingest_document_structure: 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 ingest_document_structure? +

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

Can I rate-limit ingest_document_structure? +

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

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

ingest_document_structure 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 →