opensanctions-search
Search OpenSanctions for persons, companies, vessels, or other
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/opensanctions-search.md
What opensanctions-search does on Meta Data Mcp
AI agents call opensanctions-search to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why opensanctions-search is rated Low
This tool performs a read-only search operation against OpenSanctions (a public open data API for sanctions information). It retrieves existing data without creating, modifying, deleting, or executing code. The verb 'search' and the context of querying an open data API confirm this is a Read classification.
From the tool's definition Tool is named 'opensanctions-search' and described as 'Search OpenSanctions for persons, companies, vessels, or other' — indicates a query/search operation that retrieves data from an open sanctions database without modifying it.
Attacks that exploit this kind of access
The rule that runs opensanctions-search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opensanctions-search, this is the rule to start with:
opensanctions-search 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 Meta Data Mcp, apply this rule, and every opensanctions-search call is checked against it from then on.
Questions about opensanctions-search
Search OpenSanctions for persons, companies, vessels, or other. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for opensanctions-search: 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 Meta Data Mcp. Nothing to install.
opensanctions-search 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 opensanctions-search 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 opensanctions-search. 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.
opensanctions-search is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue