check_iso_code_embargo

Check a country code against known sanction and trade embargo lists

Server Pangea MCP Server pangeacyber/pangea-mcp-server
Category Read
Risk class Low
Parameters 00 required

What check_iso_code_embargo does on Pangea MCP Server

AI agents call check_iso_code_embargo to retrieve information from Pangea MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_iso_code_embargo needs a policy

This tool performs a read-only query against embargo reference data. It takes a country code as input and returns whether that code matches known sanction or embargo lists. No data is created, modified, deleted, or financial transactions are involved. The tool's function is purely informational lookup, fitting the 'Read' category (retrieves or queries data; no side effects).

From the tool's definition Tool name 'check_iso_code_embargo' and description 'Check a country code against known sanction and trade embargo lists' indicate a lookup/query operation that retrieves embargo status information without modifying data or executing external actions.

Questions about check_iso_code_embargo

What does the check_iso_code_embargo tool do? +

Check a country code against known sanction and trade embargo lists. It is categorised as a Read tool in the Pangea MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_iso_code_embargo? +

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

What risk level is check_iso_code_embargo? +

check_iso_code_embargo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_iso_code_embargo? +

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

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

check_iso_code_embargo is provided by the Pangea MCP Server MCP server (pangeacyber/pangea-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.