High Risk →

sanctions_screener_multi

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/indi...

Risk signalsHigh parameter count (10 properties)

Part of the Mcp Knowledge server.

sanctions_screener_multi can trigger actions in Mcp Knowledge, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCP KNOWLEDGE →

Free to start. No card required.

AI agents invoke sanctions_screener_multi to trigger processes or run actions in Mcp Knowledge. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

sanctions_screener_multi can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sanctions_screener_multi": {
      "limits": [
        {
          "counter": "sanctions_screener_multi_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mcp Knowledge policy for all 271 tools.

Get this rule live on your own Mcp Knowledge server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP KNOWLEDGE →

View all 271 tools →

These attack patterns abuse exactly the kind of access sanctions_screener_multi gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so sanctions_screener_multi only ever does what you allow.

SECURE MCP KNOWLEDGE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

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 Execute tool in the Mcp Knowledge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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.

Enforce policy on every Mcp Knowledge tool call.

Deterministic rules across all 271 Mcp Knowledge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.