Screen a person, company, vessel, or crypto wallet against OFAC (US), EU, UN, and UK sanctions lists in a single call. Use this tool when: - An agent is onboarding a new counterparty or customer and needs KYC/AML verification - A payment agent is about to send funds and must verify the recipient ...
AI agents call screen_sanctions to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries external sanctions databases and returns screening results — it reads/retrieves compliance data without modifying any records or triggering financial transactions. However, severity is medium because misuse (e.g., incorrectly clearing a sanctioned entity) could have serious downstream consequences in payment or trading workflows that depend on its output.
From the tool's definition Screen a person, company, vessel, or crypto wallet against OFAC (US), EU, UN, and UK sanctions lists in a single call... Returns: match_probability, matched_lists, sanctioned_entity_details, risk_level
Attacks that exploit this kind of access
Screen a person, company, vessel, or crypto wallet against OFAC (US), EU, UN, and UK sanctions lists in a single call. Use this tool when: - An agent is onboarding a new counterparty or customer and needs KYC/AML verification - A payment agent is about to send funds and must verify the recipient is not sanctioned - A trading agent needs to verify a counterparty before executing a trade - You need to check if a crypto wallet address is linked to sanctioned entities Returns: match_probability (0-100), matched_lists, sanctioned_entity_details, risk_level (CLEAR/LOW/MEDIUM/HIGH/BLOCKED), and recommended_action. Example: screenSanctions({ name:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for screen_sanctions: 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 Omni Service Node. Nothing to install.
screen_sanctions 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_sanctions 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_sanctions. 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_sanctions is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →