law.sanctions-check
Fuzzy-match a name (person, company, vessel, aircraft) against the US Treasury OFAC SDN list. Returns ranked matches with similarity scores and sanctions program metadata. List refreshed daily.
This record as markdown: /tools/io-github-2s-io-mcp/law.sanctions-check.md
What law.sanctions-check does on Mcp
AI agents call law.sanctions-check to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why law.sanctions-check is rated Low
This is a lookup/search tool that reads from a sanctions database to check names against regulatory lists. While the output (sanctions status) has regulatory and compliance implications, the tool itself performs only read operations.
From the tool's definition Tool performs a 'fuzzy-match' query against OFAC SDN list and 'returns ranked matches' — it retrieves and queries data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs law.sanctions-check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For law.sanctions-check, this is the rule to start with:
law.sanctions-check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every law.sanctions-check call is checked against it from then on.
Questions about law.sanctions-check
Fuzzy-match a name (person, company, vessel, aircraft) against the US Treasury OFAC SDN list. Returns ranked matches with similarity scores and sanctions program metadata. List refreshed daily. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for law.sanctions-check: 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. Nothing to install.
law.sanctions-check 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 law.sanctions-check 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 law.sanctions-check. 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.
law.sanctions-check is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue