claim_docx_region

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 33 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/claim-docx-region.md

WHAT IT DOES

What claim_docx_region does on Meridian

AI agents use claim_docx_region 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
`file_path`	string	Yes	The .docx source path (the same value as the `doc` arg to update_paragraph / ingest_document).
`element_id`	string	Yes	The target element's durable id (w14:paraId or p{index} fallback) as surfaced by get_document_structure.
`session_id`	string	Yes	The calling session.

Parameters from the server's own tool schema.

RISK

Why claim_docx_region is rated Medium

This tool creates a lock/claim record on a document element, which is a reversible write operation (claims can presumably be released). It does not delete or overwrite content, execute code, or move money — it establishes a coordination state that blocks concurrent edits. The blast radius is medium: misuse could block other sessions from editing document regions, but is reversible by releasing the claim.

From the tool's definition 'Claim a specific paragraph/element by its durable element_id so another session cannot overwrite it concurrently' and 'An edit to a claimed element_id by another session is REJECTED structurally'

Risk signalsAccepts file system path (file_path)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

claim_docx_region Rate-limited

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

FAQ

Questions about claim_docx_region

What does the claim_docx_region tool do? +

[MAINTENANCE] f7ee1ba7 — Model B scoped-region claiming for .docx files. Claim a specific paragraph/element by its durable element_id (the w14:paraId surfaced by get_document_structure / update_paragraph) so another session cannot overwrite it concurrently. Two sessions can hold NON-OVERLAPPING element claims on the SAME file — the real precision benefit vs. a whole-file lock. An edit to a claimed element_id by another session is REJECTED structurally (not just advisory) at the update_paragraph level. A whole-file lock by another session blocks this claim. Returns {claimed: true, file_path, session_id, element_id} on success or {claimed: false, reason, message, conflicts} on conflict. 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 claim_docx_region accept? +

claim_docx_region accepts 3 parameters: file_path, element_id, session_id. Required: file_path, element_id, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on claim_docx_region? +

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

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

Can I rate-limit claim_docx_region? +

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

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

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