List previously captured graph snapshots, most recent first. Each entry includes its summary so you can inspect counts without diffing. Read-only. Returns JSON: { snapshots: [{ id, name, captured_at, summary }], total }.
AI agents call list_graph_snapshots to retrieve information from Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists historical snapshots of code dependency graphs. It performs a query operation with no ability to modify, delete, or execute code. The read-only designation and list/inspect functionality place it clearly in the Read category with low severity, as it only surfaces information about previously captured artifacts.
From the tool's definition Tool description explicitly states 'Read-only' and 'List previously captured graph snapshots'. Returns JSON with metadata (id, name, captured_at, summary) without side effects.
Documented attack patterns abuse exactly the kind of access list_graph_snapshots gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for list_graph_snapshots:
{
"version": "1",
"default": "deny",
"tools": {
"list_graph_snapshots": {}
}
}list_graph_snapshots is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List previously captured graph snapshots, most recent first. Each entry includes its summary so you can inspect counts without diffing. Read-only. Returns JSON: { snapshots: [{ id, name, captured_at, summary }], total }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for list_graph_snapshots: 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 Trace. Nothing to install.
list_graph_snapshots 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 list_graph_snapshots 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 list_graph_snapshots. 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.
list_graph_snapshots is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.