get_symbol_hotspots
[MAINTENANCE] Read-only: symbols claimed by 3+ distinct sessions within 14 days — a refactor/ownership smell. Optionally scope to one file.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-symbol-hotspots.md
What get_symbol_hotspots does on Meridian
AI agents call get_symbol_hotspots 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 |
|---|---|---|---|
days | integer | — | |
file_path | string | — | |
min_sessions | integer | — |
Parameters from the server's own tool schema.
Why get_symbol_hotspots is rated Low
This tool retrieves and queries persistent memory to identify refactoring hotspots based on symbol ownership patterns. It has no side effects, does not modify data, and performs analysis only. The [MAINTENANCE] tag and 'read-only' designation confirm it is a passive query tool.
From the tool's definition Tool description explicitly states 'Read-only' and 'symbols claimed by 3+ distinct sessions within 14 days' — retrieves analytic data about code symbols with no modification capability. Optionally scoped to a file, indicating query-like filtering.
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
The rule that runs get_symbol_hotspots 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_hotspots, this is the rule to start with:
get_symbol_hotspots 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_hotspots call is checked against it from then on.
Questions about get_symbol_hotspots
[MAINTENANCE] Read-only: symbols claimed by 3+ distinct sessions within 14 days — a refactor/ownership smell. Optionally scope to one file. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_symbol_hotspots accepts 3 parameters: days, file_path, min_sessions. 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_hotspots: 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_hotspots 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_hotspots 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_hotspots. 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_hotspots 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