sanctions_get_entity
Fetch a full record by entity ID (e.g. "OFAC_SDN-44705"). The ID is self-describing and includes the source; obtain it from a screening result.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sanctions-get-entity.md
What sanctions_get_entity does on Livedatalink
AI agents call sanctions_get_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 |
|---|---|---|---|
id | string | Yes | Entity ID from a screening result, e.g. "OFAC_SDN-44705". |
Parameters from the server's own tool schema.
Why sanctions_get_entity is rated Low
This tool retrieves sanctions entity records by ID from what appears to be an OFAC (Office of Foreign Assets Control) sanctions database. It has no side effects—it only queries and returns data about sanctioned entities. This is a standard Read operation.
From the tool's definition Tool description states 'Fetch a full record by entity ID', which is a retrieval operation. The word 'Fetch' indicates data retrieval without modification or deletion.
Attacks that exploit this kind of access
The rule that runs sanctions_get_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_get_entity, this is the rule to start with:
sanctions_get_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_get_entity call is checked against it from then on.
Questions about sanctions_get_entity
Fetch a full record by entity ID (e.g. "OFAC_SDN-44705"). The ID is self-describing and includes the source; obtain it from a screening result. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sanctions_get_entity accepts 1 parameter: id. Required: 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 sanctions_get_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_get_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_get_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_get_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_get_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