sanctions_screen_entity
Screen a single name or entity against the four major sanctions / denied-party lists (OFAC SDN, EU consolidated, UN consolidated, BIS DPL). Returns matches with confidence scores. This call uses the standard hosted query allowance; the free tier includes 1,000 queries/month and paid plans use the...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-screen-entity.md
What sanctions_screen_entity does on Livedatalink
AI agents call sanctions_screen_entity 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 |
|---|---|---|---|
name | string | Yes | Name or entity string to screen. |
limit | number | — | Maximum matches to return. Defaults vary per tool. |
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_entity is rated Low
Even though sanctions_screen_entity 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 sanctions_screen_entity 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_entity, this is the rule to start with:
sanctions_screen_entity 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_entity call is checked against it from then on.
Questions about sanctions_screen_entity
Screen a single name or entity against the four major sanctions / denied-party lists (OFAC SDN, EU consolidated, UN consolidated, BIS DPL). Returns matches with confidence scores. This call uses the standard hosted query allowance; the free tier includes 1,000 queries/month and paid plans use the published plan pricing. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sanctions_screen_entity accepts 4 parameters: name, limit, sources, threshold. Required: name. 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_entity: 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_entity 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_entity 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_entity. 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_entity 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