data_sanctions_screen
Sanctions, PEP & watchlist screen for any person or company across OFAC, EU, UK, UN + 100+ lists (OpenSanctions). The canonical KYC/KYB gate — call before onboarding, paying, or transacting with any counterparty. Example call: {"name": "Gazprom"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/data-sanctions-screen.md
What data_sanctions_screen does on GoCreative Agent API
AI agents call data_sanctions_screen to retrieve information from GoCreative Agent API 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 |
Parameters from the server's own tool schema.
Why data_sanctions_screen is rated Low
This tool retrieves compliance data from public and regulatory sanctions lists (OFAC, EU, UK, UN, OpenSanctions) without creating, modifying, or deleting any data. It performs read-only queries to determine if a person or company appears on watchlists. While the results inform high-stakes decisions (KYC/KYB gating), the tool itself only reads and returns information.
From the tool's definition Tool description states it 'screens' and 'calls before onboarding, paying, or transacting' — a lookup/query operation against sanctions and watchlist databases.
Attacks that exploit this kind of access
The rule that runs data_sanctions_screen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_sanctions_screen, this is the rule to start with:
data_sanctions_screen 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 GoCreative Agent API, apply this rule, and every data_sanctions_screen call is checked against it from then on.
Questions about data_sanctions_screen
Sanctions, PEP & watchlist screen for any person or company across OFAC, EU, UK, UN + 100+ lists (OpenSanctions). The canonical KYC/KYB gate — call before onboarding, paying, or transacting with any counterparty. Example call: {"name": "Gazprom"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
data_sanctions_screen accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for data_sanctions_screen: 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 GoCreative Agent API. Nothing to install.
data_sanctions_screen 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 data_sanctions_screen 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 data_sanctions_screen. 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.
data_sanctions_screen is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue