source_snapshot_status
Return the current immutable ingestion manifest for one self-hosted LiveDataLink source. Includes official source URL, retrieval time, rights class, byte counts, SHA-256 evidence, record counts when the transformer has computed them, and whether the raw artifact is stored as one object or reconst...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/source-snapshot-status.md
What source_snapshot_status does on Livedatalink
AI agents call source_snapshot_status 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
source_id | string | Yes | Catalog source id, for example cisa-kev, leie, fda-orange-book, ntsb-aviation, or cfpb-complaints. |
Parameters from the server's own tool schema.
Why source_snapshot_status is rated Low
Even though source_snapshot_status 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.
Attacks that exploit this kind of access
The rule that runs source_snapshot_status 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_status, this is the rule to start with:
source_snapshot_status 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 Livedatalink, apply this rule, and every source_snapshot_status call is checked against it from then on.
Questions about source_snapshot_status
Return the current immutable ingestion manifest for one self-hosted LiveDataLink source. Includes official source URL, retrieval time, rights class, byte counts, SHA-256 evidence, record counts when the transformer has computed them, and whether the raw artifact is stored as one object or reconstructable chunks. This is provenance/status, not a raw-data export. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
source_snapshot_status accepts 1 parameter: source_id. Required: source_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for source_snapshot_status: 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.
source_snapshot_status 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 source_snapshot_status 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 source_snapshot_status. 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.
source_snapshot_status 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.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue