acquire_docx_document_lease
[MAINTENANCE] 6507e83a — Whole-document cross-process lease for .docx files, the counterpart claim_docx_region never provided (that tool hard-requires a specific element_id). Use this when a session needs to rewrite an ENTIRE document (a bulk restructure, a canonical-merge promotion) and must blo...
This record as markdown: /tools/io-github-ajc3xc-meridian/acquire-docx-document-lease.md
What acquire_docx_document_lease does on Meridian
AI agents call acquire_docx_document_lease to permanently remove resources in Meridian, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_path | string | Yes | The .docx source path. |
session_id | string | Yes | The calling session. |
Parameters from the server's own tool schema.
Why acquire_docx_document_lease is rated Critical
An AI agent that decides to call acquire_docx_document_lease doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meridian is gone. There is no undo for destructive operations.
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
The rule that runs acquire_docx_document_lease 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 acquire_docx_document_lease, this is the rule to start with:
acquire_docx_document_lease is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every acquire_docx_document_lease call is checked against it from then on.
Questions about acquire_docx_document_lease
[MAINTENANCE] 6507e83a — Whole-document cross-process lease for .docx files, the counterpart claim_docx_region never provided (that tool hard-requires a specific element_id). Use this when a session needs to rewrite an ENTIRE document (a bulk restructure, a canonical-merge promotion) and must block out every other writer, not just one element. Blocked by another live session's whole-file lock (claim_file) OR ANY other live session's claim on the file (lease or scoped element) — a whole-document lease requires the document be free of every other session's claims first. Once held, blocks every other session's writes (via check_docx_region_write_conflict, the same gate update_paragraph and the meridian-docs tunnel relay already enforce) and new claim_docx_region attempts on this file until released or expired (same TTL as every other claim in this module). Returns {leased: true, file_path, session_id} on success or {leased: false, reason, message, ...} on conflict — never raises. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata -- including task log entries, pinned decisions, sprint items, notes, handoff/goal state, and HITL queue items -- are sent to and stored in Meridian's service, in an isolated per-tenant Postgres database (Neon); self-hosted deployments keep the same categories in the configured local SQLite/Postgres database. This data is visible in the dashboard and API, and may resurface in later project context or handoffs. Notes and pinned decisions can be deleted individually; task log entries and sprint items can be deleted via the dashboard/API (not exposed as an agent-facing tool); HITL queue items and handoff state have no per-record delete. Full removal of any of this data is available via project or account deletion, using the documented controls. Do not include secrets. It is categorised as a Destructive tool in the Meridian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
acquire_docx_document_lease accepts 2 parameters: file_path, session_id. Required: file_path, session_id. 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 acquire_docx_document_lease: 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.
acquire_docx_document_lease is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the acquire_docx_document_lease 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 acquire_docx_document_lease. 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.
acquire_docx_document_lease 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.
Across the catalogue