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

get_file_claims

[SUPPORT] Read-only: show active claims on a file — the whole-file lock (with the holder's session name, if any) plus any symbol-level claims. Use to check who owns a file before editing it. Pass project_id (and optional symbol) to also get a code_notes list of code-anchored notes (kind='code') f...

SERVERMeridian SOURCE@meridianmcp/mcp
Low RISK CLASS
Category Read
Parameters 41 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-file-claims.md

What get_file_claims does on Meridian

AI agents call get_file_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
symbol string Optional symbol to scope code-anchored notes to (requires project_id).
file_path string Yes
project_id string Include code-anchored notes (kind='code') for this project/path in the response.
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.

Why get_file_claims is rated Low

This is a straightforward information retrieval operation that queries the state of file locks and claims. It has no side effects, creates no modifications, and cannot be misused to cause significant harm. Low severity reflects the informational nature of the output and limited blast radius if an AI agent calls it repeatedly or maliciously.

From the tool's definition Tool is explicitly marked '[SUPPORT] Read-only' and described as 'show active claims on a file' with the function to 'check who owns a file before editing it'. It retrieves and displays lock/claim state and code-anchored notes without modifying any data.

Risk signalsAccepts file system path (file_path)

Questions about get_file_claims

What does the get_file_claims tool do? +

[SUPPORT] Read-only: show active claims on a file — the whole-file lock (with the holder's session name, if any) plus any symbol-level claims. Use to check who owns a file before editing it. Pass project_id (and optional symbol) to also get a code_notes list of code-anchored notes (kind='code') for that path. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_file_claims accept? +

get_file_claims accepts 4 parameters: symbol, file_path, project_id, project_name. 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_file_claims? +

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

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

Can I rate-limit get_file_claims? +

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

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

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