dual_use_export_risk_mapper

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/dual-use-export-risk-mapper.md

WHAT IT DOES

What dual_use_export_risk_mapper does on Mcp Knowledge

AI agents call dual_use_export_risk_mapper to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`bomItems`	array	Yes
`includeSources`	boolean	—

Parameters from the server's own tool schema.

RISK

Why dual_use_export_risk_mapper is rated Low

The tool performs read/query operations by analyzing input data (part numbers, descriptions, HS codes) against regulatory databases and returning a risk assessment report. It does not modify data, execute code, delete anything, or move money. It is an intelligence/compliance lookup tool. Severity is medium because misclassification of export risk could have legal or regulatory consequences.

From the tool's definition analyzes bills of materials (BOMs) against EU dual-use export control lists and ICAO/IMO restricted items data... receive a risk assessment with actionable insights... Output includes risk levels, applicable regulations, and source references for audit trails

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dual_use_export_risk_mapper safely

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

dual_use_export_risk_mapper Allowed

dual_use_export_risk_mapper is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dual_use_export_risk_mapper": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dual_use_export_risk_mapper

What does the dual_use_export_risk_mapper tool do? +

As a COO, quickly assess export compliance risks for components in your supply chain. This tool analyzes bills of materials (BOMs) against EU dual-use export control lists and ICAO/IMO restricted items data. Input a list of part numbers, descriptions, or HS codes to receive a risk assessment with actionable insights. Output includes risk levels, applicable regulations, and source references for audit trails. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does dual_use_export_risk_mapper accept? +

dual_use_export_risk_mapper accepts 3 parameters: async, bomItems, includeSources. Required: bomItems. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dual_use_export_risk_mapper? +

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

What risk level is dual_use_export_risk_mapper? +

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

Can I rate-limit dual_use_export_risk_mapper? +

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

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

dual_use_export_risk_mapper is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

aiva_get_churn_risk on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →