ofac.sdn.aliases
Get all known aliases (alternate names) for a specific OFAC SDN entity by its entity number. Returns each alias with its type (aka = also known as, fka = formerly known as, nka = now known as) and the alternate name. Use ofac.sdn.search first to find the entity number (ent_num) for the entity you...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ofac.sdn.aliases.md
What ofac.sdn.aliases does on Apibase
AI agents call ofac.sdn.aliases to retrieve information from Apibase 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 |
|---|---|---|---|
ent_num | integer | Yes | OFAC entity number (ent_num) of the SDN entry to look up aliases for. Obtain this from ofac.sdn.search results (the "ent_num" field on each match). |
Parameters from the server's own tool schema.
Why ofac.sdn.aliases is rated Low
Retrieves public OFAC sanctions data for screening purposes; no data modification or side effects.
From the tool's definition Get all known aliases for a specific OFAC SDN entity by its entity number. Returns each alias with its type.
Attacks that exploit this kind of access
The rule that runs ofac.sdn.aliases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ofac.sdn.aliases, this is the rule to start with:
ofac.sdn.aliases 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 Apibase, apply this rule, and every ofac.sdn.aliases call is checked against it from then on.
Questions about ofac.sdn.aliases
Get all known aliases (alternate names) for a specific OFAC SDN entity by its entity number. Returns each alias with its type (aka = also known as, fka = formerly known as, nka = now known as) and the alternate name. Use ofac.sdn.search first to find the entity number (ent_num) for the entity you are screening. Aliases are critical for comprehensive sanctions screening — sanctioned entities often operate under multiple names. Example: entity 36 (AEROCARIBBEAN AIRLINES) has alias "AERO-CARIBBEAN". Data source: OFAC SDN Alternate Names List — US Treasury, public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ofac.sdn.aliases accepts 1 parameter: ent_num. Required: ent_num. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ofac.sdn.aliases: 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 Apibase. Nothing to install.
ofac.sdn.aliases 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 ofac.sdn.aliases 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 ofac.sdn.aliases. 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.
ofac.sdn.aliases is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue