screenSanctions

SERVERAPI Ninjas SOURCEhttps://mcp.api-ninjas.com/mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-api-ninjas-mcp/screensanctions.md

WHAT IT DOES

What screenSanctions does on API Ninjas

AI agents use screenSanctions to create or update resources in API Ninjas, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API Ninjas environment.

Parameter	Type	Required	Description
`dob`	string	—	Date of birth (YYYY-MM-DD) to filter individual matches. Loose match: ±1 year. Developer tier and above.
`name`	string	Yes	Name to screen. Full name, ordering doesn't matter.
`country`	string	—	ISO 3166-1 alpha-2 country code to filter results by nationality/jurisdiction. Developer tier and above.
`sources`	string	—	Comma-separated subset of OFAC,EU,UK,UN,AU to scope the screen to specific lists. Developer tier and above.
`min_score`	integer	—	Minimum confidence score (0-100) to return. Default 70. Developer tier and above.
`entity_type`	string	—	Restrict the screen to a specific entity type. Vessel and aircraft are Business tier and above.
`nationality`	string	—	ISO 3166-1 alpha-2 nationality filter. Developer tier and above.

Parameters from the server's own tool schema.

RISK

Why screenSanctions is rated Medium

An AI agent can call screenSanctions faster than any human can review: one bad instruction and it creates or modifies resources in API Ninjas by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs screenSanctions safely

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

screenSanctions Rate-limited

screenSanctions stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "screenSanctions": {
      "limits": [
        {
          "counter": "screensanctions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about screenSanctions

What does the screenSanctions tool do? +

Returns ranked matches against the configured government sanctions lists. The set of lists and entity types available depends on subscription tier — Free covers OFAC SDN individuals only, Developer adds EU and entities, Business adds UK/UN/AU and vessels/aircraft. It is categorised as a Write tool in the API Ninjas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does screenSanctions accept? +

screenSanctions accepts 7 parameters: dob, name, country, sources, min_score, entity_type, nationality. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on screenSanctions? +

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

What risk level is screenSanctions? +

screenSanctions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit screenSanctions? +

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

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

screenSanctions is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API Ninjas, and thousands of servers like it.

This server

All 244 API Ninjas tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →