get_symbol_claims
[MAINTENANCE] Read-only: list symbol-level claims on a file (who owns which class/function/method line ranges).
This record as markdown: /tools/io-github-ajc3xc-meridian/get-symbol-claims.md
What get_symbol_claims does on Meridian
AI agents call get_symbol_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_path | string | Yes |
Parameters from the server's own tool schema.
Why get_symbol_claims is rated Low
This tool queries and retrieves information about symbol ownership claims (class/function/method metadata) on a file. It performs no modifications, deletions, or external operations—purely a data retrieval operation. The explicit 'read-only' marking and 'list' action place it firmly in the Read category.
From the tool's definition Tool name 'get_symbol_claims' with description explicitly marked '[MAINTENANCE] Read-only: list symbol-level claims on a file'. The verb 'list' and 'read-only' designation confirm retrieval without side effects.
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
The rule that runs get_symbol_claims 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 get_symbol_claims, this is the rule to start with:
get_symbol_claims 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 get_symbol_claims call is checked against it from then on.
Questions about get_symbol_claims
[MAINTENANCE] Read-only: list symbol-level claims on a file (who owns which class/function/method line ranges). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_symbol_claims accepts 1 parameter: file_path. Required: file_path. 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 get_symbol_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.
get_symbol_claims 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 get_symbol_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.
Set action: deny in the PolicyLayer policy for get_symbol_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.
get_symbol_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.
This server
Across the catalogue