find_orphaned_docx_staged_files
[MAINTENANCE] 6507e83a — Maintenance diagnostic: detect staged-DOCX temp files (.meridian-docx-stage-*.tmp) left behind by a process that crashed between STAGE and PROMOTE inside meridian.doc_store's write transaction. Purely a detection utility — never deletes or touches anything it finds. Retur...
This record as markdown: /tools/io-github-ajc3xc-meridian/find-orphaned-docx-staged-files.md
What find_orphaned_docx_staged_files does on Meridian
AI agents call find_orphaned_docx_staged_files 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 |
|---|---|---|---|
directory | string | Yes | Directory to scan (typically a .docx's own parent directory). |
max_age_seconds | number | — | Age threshold in seconds for likely_orphan=true. Default 3600 (1 hour). |
Parameters from the server's own tool schema.
Why find_orphaned_docx_staged_files is rated Low
Even though find_orphaned_docx_staged_files only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs find_orphaned_docx_staged_files 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 find_orphaned_docx_staged_files, this is the rule to start with:
find_orphaned_docx_staged_files 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 find_orphaned_docx_staged_files call is checked against it from then on.
Questions about find_orphaned_docx_staged_files
[MAINTENANCE] 6507e83a — Maintenance diagnostic: detect staged-DOCX temp files (.meridian-docx-stage-*.tmp) left behind by a process that crashed between STAGE and PROMOTE inside meridian.doc_store's write transaction. Purely a detection utility — never deletes or touches anything it finds. Returns a list of {path, size_bytes, age_seconds, likely_orphan}, oldest first. A file younger than max_age_seconds is reported but not flagged likely_orphan (it may be an active, in-flight promotion). 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 Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
find_orphaned_docx_staged_files accepts 2 parameters: directory, max_age_seconds. Required: directory. 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 find_orphaned_docx_staged_files: 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.
find_orphaned_docx_staged_files 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 find_orphaned_docx_staged_files 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 find_orphaned_docx_staged_files. 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.
find_orphaned_docx_staged_files 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