snapshot_graph_metrics
[MAINTENANCE] Record a code-graph snapshot for a session (node count, edge count, hotspot count, file churn). Call at session start and end to enable get_graph_diff comparisons. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in M...
This record as markdown: /tools/io-github-ajc3xc-meridian/snapshot-graph-metrics.md
What snapshot_graph_metrics does on Meridian
AI agents use snapshot_graph_metrics to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | — | |
session_id | string | Yes | |
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 snapshot_graph_metrics is rated Medium
This tool writes/records snapshot metrics to persistent storage (SQLite/Postgres or hosted service). It creates a new data record at session start/end for later diff comparisons. There is no deletion, execution of code, or financial action involved. The blast radius is low — misuse could pollute graph history with incorrect metrics but is reversible via deletion controls mentioned in the description.
From the tool's definition Record a code-graph snapshot for a session (node count, edge count, hotspot count, file churn)... supplied text and project/session metadata are sent to and stored in Meridian's service
Attacks that exploit this kind of access
The rule that runs snapshot_graph_metrics 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 snapshot_graph_metrics, this is the rule to start with:
snapshot_graph_metrics stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 snapshot_graph_metrics call is checked against it from then on.
Questions about snapshot_graph_metrics
[MAINTENANCE] Record a code-graph snapshot for a session (node count, edge count, hotspot count, file churn). Call at session start and end to enable get_graph_diff comparisons. 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 Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
snapshot_graph_metrics accepts 3 parameters: project_id, session_id, project_name. Required: session_id. 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 snapshot_graph_metrics: 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.
snapshot_graph_metrics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snapshot_graph_metrics 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 snapshot_graph_metrics. 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.
snapshot_graph_metrics 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