sanctions_screener_multi

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 104 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/sanctions-screener-multi.md

WHAT IT DOES

What sanctions_screener_multi does on Mcp Knowledge

AI agents call sanctions_screener_multi to retrieve information from Mcp Knowledge 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
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`address`	string	—
`aliases`	array	—
`entity_name`	string	Yes
`entity_type`	string	Yes
`context_note`	string	—
`date_of_birth`	string	—
`jurisdiction_focus`	string	Yes
`country_of_registration`	string	—
`adverse_media_lookback_days`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why sanctions_screener_multi is rated Low

The tool queries multiple external sanctions databases (OFAC, EU, UN, HMT, SECO, SEMA, PEP, adverse media) and returns a composite risk score and evidence trail. This is a read/query operation with no indication of writing or modifying data.

From the tool's definition 'run full OFAC + EU + UK HMT + UN + SECO + Canada SEMA + PEP + adverse media screening with composite risk score and evidence trail' — the tool retrieves and aggregates data from multiple sanctions watchlists and returns a structured report

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sanctions_screener_multi safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sanctions_screener_multi, this is the rule to start with:

sanctions_screener_multi Allowed

sanctions_screener_multi is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sanctions_screener_multi": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every sanctions_screener_multi call is checked against it from then on.

FAQ

Questions about sanctions_screener_multi

What does the sanctions_screener_multi tool do? +

Screening Sanctions Multi-listes — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: For <entity>, run full OFAC + EU + UK HMT + UN + SECO + Canada SEMA + PEP + adverse media screening with composite risk score and evidence trail. · Is <company/individual> on any major international sanctions list? · What is the composite AML risk score for <entity> across all major watchlists? · Screen this M&A target / supplier / LP against all major sanctions lists and give me a compliance recommendation. · Is <entity> a PEP or associated with a PEP? What Enhanced Due Diligence is required? Reference case: Veridian Trading Co. LLC (Cyprus) — 7 listes · PEP check · adverse media 2 ans · composite 52/100 · escalate-to-compliance → EDD requis. Inputs are validated server-side — send the documented case fields. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does sanctions_screener_multi accept? +

sanctions_screener_multi accepts 10 parameters: async, address, aliases, entity_name, entity_type, context_note, date_of_birth, jurisdiction_focus, country_of_registration, adverse_media_lookback_days. Required: entity_name, entity_type, jurisdiction_focus, adverse_media_lookback_days. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sanctions_screener_multi? +

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

What risk level is sanctions_screener_multi? +

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

Can I rate-limit sanctions_screener_multi? +

Yes. Add a rate_limit block to the sanctions_screener_multi 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 sanctions_screener_multi completely? +

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

sanctions_screener_multi is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →