New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

screen_sanctions_lists

Use BEFORE any payment, contract or onboarding involving the name. AML sanctions screening of a person or company name against 6 official sanctions lists (UN consolidated, EU FSF, US OFAC SDN, UK Sanctions List, French asset-freeze register, Swiss SECO list). Returns fuzzy matches with a 0-100 co...

SERVERSirenic SOURCEhttps://api.sirenic.eu/mcp
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eu-sirenic-sirenic/screen-sanctions-lists.md

What screen_sanctions_lists does on Sirenic

AI agents call screen_sanctions_lists to retrieve information from Sirenic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
name string Yes Person or company name to screen
api_key string — Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=ap
x_payment string — Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.
birth_year string — Optional birth year (YYYY) to refine person matches

Parameters from the server's own tool schema.

Why screen_sanctions_lists is rated Low

Even though screen_sanctions_lists only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHandles credentials or secrets (api_key)

Questions about screen_sanctions_lists

What does the screen_sanctions_lists tool do? +

Use BEFORE any payment, contract or onboarding involving the name. AML sanctions screening of a person or company name against 6 official sanctions lists (UN consolidated, EU FSF, US OFAC SDN, UK Sanctions List, French asset-freeze register, Swiss SECO list). Returns fuzzy matches with a 0-100 confidence score — never a bare yes/no. Each list is reported with its entry count, its publication date and what that date means (official upstream publication vs. Sirenic ingestion — OFAC publishes none). Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.

What parameters does screen_sanctions_lists accept? +

screen_sanctions_lists accepts 4 parameters: name, api_key, x_payment, birth_year. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on screen_sanctions_lists? +

Register the Sirenic MCP server in PolicyLayer and add a rule for screen_sanctions_lists: 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 Sirenic. Nothing to install.

What risk level is screen_sanctions_lists? +

screen_sanctions_lists is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit screen_sanctions_lists? +

Yes. Add a rate_limit block to the screen_sanctions_lists 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.

How do I block screen_sanctions_lists completely? +

Set action: deny in the PolicyLayer policy for screen_sanctions_lists. 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.

What MCP server provides screen_sanctions_lists? +

screen_sanctions_lists is provided by the Sirenic MCP server (https://api.sirenic.eu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sirenic, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sirenic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.