ofac.sdn.search
Search the US Treasury OFAC Specially Designated Nationals and Blocked Persons (SDN) list by name. Returns matching entities with their entity number, type (individual/entity/vessel/aircraft), sanctions program code, title, and remarks. Filter by type (individual, entity, vessel, aircraft) and/or...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ofac.sdn.search.md
What ofac.sdn.search does on Apibase
AI agents call ofac.sdn.search 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 |
|---|---|---|---|
name | string | Yes | Name to search for in the OFAC SDN list (case-insensitive substring match). Examples: "GAZPROM", "Vladimir Putin", "Bank Melli Iran". Use the most distinctive p |
type | string | — | Filter by SDN entity type. "individual" = natural persons, "entity" = companies/organisations, "vessel" = ships, "aircraft" = aircraft. Omit to search all types |
limit | integer | — | Maximum number of matches to return (default 20, max 50). |
program | string | — | Filter by OFAC sanctions program code (uppercase). Examples: "IRAN", "RUSSIA", "CUBA", "SDN", "DPRK", "CYBER", "UKRAINE-EO13685". Use ofac.meta.programs to see |
Parameters from the server's own tool schema.
Why ofac.sdn.search is rated Low
Queries public compliance database for sanctions screening; read-only with no side effects.
From the tool's definition Search the US Treasury OFAC SDN list by name. Returns matching entities.
Attacks that exploit this kind of access
The rule that runs ofac.sdn.search 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.search, this is the rule to start with:
ofac.sdn.search 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.search call is checked against it from then on.
Questions about ofac.sdn.search
Search the US Treasury OFAC Specially Designated Nationals and Blocked Persons (SDN) list by name. Returns matching entities with their entity number, type (individual/entity/vessel/aircraft), sanctions program code, title, and remarks. Filter by type (individual, entity, vessel, aircraft) and/or sanctions program (IRAN, RUSSIA, CUBA, SDN, DPRK, CYBER, etc.). Use this for AML/KYC compliance screening, sanctions risk assessment, and due diligence workflows. Matching is case-insensitive substring search — search by any distinctive part of the name. Use ofac.meta.programs to see all available program codes. Data source: US Treasury OFAC — public domain, updated on business days. No API key required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ofac.sdn.search accepts 4 parameters: name, type, limit, program. Required: name. 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.search: 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.search 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.search 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.search. 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.search 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