sanctions_screen_address
Match a physical address against listed addresses. Useful for KYC / supplier vetting when the counterparty's name is generic but the address is distinctive.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-screen-address.md
What sanctions_screen_address does on Livedatalink
AI agents call sanctions_screen_address 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. |
address | string | Yes | Free-form address string. |
sources | array | — | Restrict screening to a subset of source lists. Defaults to all four. Allowed: OFAC_SDN, EU_CFSP, UN_SC, BIS_DPL. |
threshold | number | — | Minimum confidence score (0..1) for a result to be returned. Defaults to 0.85. |
Parameters from the server's own tool schema.
Why sanctions_screen_address is rated Low
This is a screening/lookup tool that reads from a sanctions database to check whether an address matches known sanctioned entities. No data is created, modified, or deleted; no code is executed; no financial transactions occur. The operation is purely informational and has no side effects beyond returning match results.
From the tool's definition Tool performs 'Match...against listed addresses' and is described as useful for 'KYC / supplier vetting' — it queries/retrieves data from sanctions lists without modifying, creating, or deleting any records.
Attacks that exploit this kind of access
The rule that runs sanctions_screen_address 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_screen_address, this is the rule to start with:
sanctions_screen_address 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_screen_address call is checked against it from then on.
Questions about sanctions_screen_address
Match a physical address against listed addresses. Useful for KYC / supplier vetting when the counterparty's name is generic but the address is distinctive. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sanctions_screen_address accepts 4 parameters: limit, address, sources, threshold. Required: address. 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_screen_address: 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_screen_address 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_screen_address 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_screen_address. 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_screen_address 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