New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_docx_region_claims

[MAINTENANCE] f7ee1ba7 — Read-only: list active scoped docx-region claims on a file (who owns which element_ids). Use before update_paragraph to see whether the target element is claimed. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and s...

SERVERMeridian SOURCE@meridianmcp/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-docx-region-claims.md

What get_docx_region_claims does on Meridian

AI agents call get_docx_region_claims 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.

ParameterTypeRequiredDescription
file_path string Yes The .docx source path.

Parameters from the server's own tool schema.

Why get_docx_region_claims is rated Low

This tool queries and returns existing data (who owns which element_ids) with no side effects. The description of persistent storage behavior is a transparency note about where data resides, not an action performed by this tool. The tool itself performs only retrieval/inspection, placing it squarely in the Read category.

From the tool's definition Tool description explicitly states 'Read-only: list active scoped docx-region claims on a file'. It retrieves metadata about ownership of elements without modifying state.

Risk signalsAccepts file system path (file_path)

Questions about get_docx_region_claims

What does the get_docx_region_claims tool do? +

[MAINTENANCE] f7ee1ba7 — Read-only: list active scoped docx-region claims on a file (who owns which element_ids). Use before update_paragraph to see whether the target element is claimed. 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 Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_docx_region_claims accept? +

get_docx_region_claims accepts 1 parameter: file_path. Required: file_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_docx_region_claims? +

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

get_docx_region_claims is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_docx_region_claims? +

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

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

get_docx_region_claims 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meridian's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.