Screen a person or organisation for ADVERSE MEDIA and SANCTIONS/PEP exposure (KYC/AML). USE THIS WHEN onboarding or due-diligence asks: does this subject appear in negative news (fraud, money laundering, bribery, sanctions, trafficking, enforcement action), or on a sanctions / politically-exposed...
AI agents call screen_adverse_media to retrieve information from OpenWarrant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dob | object | — | |
url | object | — | |
name | object | — | |
role | object | — | |
aliases | object | — | |
country | object | — | |
employer | object | — | |
filename | string | — | |
bytes_b64 | object | — |
Parameters from the server's own tool schema.
Despite the compliance/KYC context, this tool retrieves and queries information without modifying, deleting, or executing external operations. It reads from external databases (adverse media, sanctions, PEP registries) to return screening results. While the severity is high due to the sensitive nature of the data accessed and potential for misuse in targeting individuals or organizations, the category is Read.
From the tool's definition Tool description states it performs screening to 'detect' and 'identify' whether a person appears in adverse media lists, sanctions lists, or PEP lists.
Risk signalsAccepts file system path (filename) · Accepts URL/endpoint input (url)
Attacks that exploit this kind of access
Screen a person or organisation for ADVERSE MEDIA and SANCTIONS/PEP exposure (KYC/AML). USE THIS WHEN onboarding or due-diligence asks: does this subject appear in negative news (fraud, money laundering, bribery, sanctions, trafficking, enforcement action), or on a sanctions / politically-exposed-person list? Pairs naturally after verify_identity. Identify the subject ONE of two ways: pass name (plus any of dob as YYYY-MM-DD, country, aliases, employer, role — these sharpen matching and cut same-name false positives), OR pass an identity document via url/bytes_b64 (+filename) and the subject is read from it. Returns {subject, sanctions{...}, adverse_media{...}, risk_flag, headline, limitations}: sanctions candidates are corroboration-gated (a name-only hit is possible, NEVER confirmed — one common name matches several different people); media hits are entity-disambiguated and classified, with same-name articles surfaced under excluded. This is screening COVERAGE, not a determination — a hit means "review this", not "guilty"; "nothing found" is not a clean record. Stateless — nothing is stored. It is categorised as a Read tool in the OpenWarrant MCP Server, which means it retrieves data without modifying state.
screen_adverse_media accepts 9 parameters: dob, url, name, role, aliases, country, employer, filename, bytes_b64. The full parameter table on this page comes from the server's own tool schema.
Register the OpenWarrant MCP server in PolicyLayer and add a rule for screen_adverse_media: 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 OpenWarrant. Nothing to install.
screen_adverse_media 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 screen_adverse_media 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 screen_adverse_media. 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.
screen_adverse_media is provided by the OpenWarrant MCP server (https://www.stipple.sh/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →