sanctions_get_changes
Return entities added or updated since a given ISO date for a chosen source list. The four official lists do not all expose a public delta feed, so this filters the cached snapshot by listedOn.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-get-changes.md
What sanctions_get_changes does on Livedatalink
AI agents call sanctions_get_changes 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 |
|---|---|---|---|
limit | number | — | Maximum matches to return. Defaults vary per tool. |
since | string | Yes | ISO date string (e.g. 2026-01-01) to compute the delta from. |
source | string | Yes |
Parameters from the server's own tool schema.
Why sanctions_get_changes is rated Low
This tool retrieves sanctions list changes from a cached snapshot filtered by date. It performs a query operation on read-only data (official sanctions lists), with no capability to modify, delete, or execute external operations. The use of 'get' and 'Return' confirms it is a data retrieval function.
From the tool's definition Tool name contains 'get' and description states 'Return entities...filters the cached snapshot' — both indicate querying/retrieval of existing data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs sanctions_get_changes 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 sanctions_get_changes, this is the rule to start with:
sanctions_get_changes 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 sanctions_get_changes call is checked against it from then on.
Questions about sanctions_get_changes
Return entities added or updated since a given ISO date for a chosen source list. The four official lists do not all expose a public delta feed, so this filters the cached snapshot by listedOn. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sanctions_get_changes accepts 3 parameters: limit, since, source. Required: since, source. 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 sanctions_get_changes: 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.
sanctions_get_changes 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 sanctions_get_changes 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 sanctions_get_changes. 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.
sanctions_get_changes 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