source_snapshot_list

SERVERLivedatalink SOURCEhttps://livedatalink.ai/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/io-github-blackboxfoundry-livedatalink/source-snapshot-list.md

WHAT IT DOES

What source_snapshot_list does on Livedatalink

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

RISK

Why source_snapshot_list is rated Low

Even though source_snapshot_list only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs source_snapshot_list safely

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

source_snapshot_list Allowed

source_snapshot_list 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": {
    "source_snapshot_list": {}
  }
}

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

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

FAQ

Questions about source_snapshot_list

What does the source_snapshot_list tool do? +

List the source ids that currently have versioned raw snapshots in LiveDataLink's private R2 evidence store. This reports hosted ingestion coverage; it does not imply that every catalog source already has a normalized query tool. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on source_snapshot_list? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for source_snapshot_list: 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 Livedatalink. Nothing to install.

What risk level is source_snapshot_list? +

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

Can I rate-limit source_snapshot_list? +

Yes. Add a rate_limit block to the source_snapshot_list 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 source_snapshot_list completely? +

Set action: deny in the PolicyLayer policy for source_snapshot_list. 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 source_snapshot_list? +

source_snapshot_list is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink 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 →