sanctions_screen_batch
Screen up to 50 names in a single call. Returns one result block per input, in input order. Each name counts as one screen for billing purposes.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-screen-batch.md
What sanctions_screen_batch does on Livedatalink
AI agents call sanctions_screen_batch 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. |
names | array | Yes | Array of names to screen. Max 50. |
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_batch is rated Low
This is a lookup/query operation that screens names against sanctions lists. While the underlying data (sanctions information) is sensitive, the tool itself only reads and retrieves information. It does not create, modify, delete records, execute code, or trigger financial actions. The billing model (counting screens) reflects usage tracking, not financial transactions.
From the tool's definition Tool performs batch name screening against sanctions databases, returning results without modifying any data. The description specifies it 'returns one result block per input' and counts against billing—purely informational operations.
Attacks that exploit this kind of access
The rule that runs sanctions_screen_batch 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_batch, this is the rule to start with:
sanctions_screen_batch 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_batch call is checked against it from then on.
Questions about sanctions_screen_batch
Screen up to 50 names in a single call. Returns one result block per input, in input order. Each name counts as one screen for billing purposes. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sanctions_screen_batch accepts 4 parameters: limit, names, sources, threshold. Required: names. 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_batch: 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_batch 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_batch 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_batch. 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_batch 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