list_graph_snapshots

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/list-graph-snapshots.md

WHAT IT DOES

What list_graph_snapshots does on Trace

AI agents call list_graph_snapshots to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_graph_snapshots is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_graph_snapshots safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_graph_snapshots, this is the rule to start with:

list_graph_snapshots Allowed

list_graph_snapshots is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_graph_snapshots": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every list_graph_snapshots call is checked against it from then on.

FAQ

Questions about list_graph_snapshots

What does the list_graph_snapshots tool do? +

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.

How do I enforce a policy on list_graph_snapshots? +

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.

What risk level is list_graph_snapshots? +

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

Can I rate-limit list_graph_snapshots? +

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.

How do I block list_graph_snapshots completely? +

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.

What MCP server provides list_graph_snapshots? +

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.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →