dual_use_tech_diversion_monitor
Asynchronous T5-level tool for COO persona to detect unauthorized diversion of dual-use technologies. Cross-references shipment manifests, EU sanctions lists, and ICAO/IMO transport data to identify suspicious transfers. Inputs: shipment IDs, company identifiers, or geographic routes. Outputs str...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/dual-use-tech-diversion-monitor.md
What dual_use_tech_diversion_monitor does on Mcp Knowledge
AI agents call dual_use_tech_diversion_monitor 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 |
route | object | — | |
companyId | string | — | Company registration number or tax identifier |
shipmentId | string | — | Unique shipment identifier (e.g., bill of lading number) |
techCategory | string | — | Dual-use technology category |
Parameters from the server's own tool schema.
Why dual_use_tech_diversion_monitor is rated Low
This tool queries and correlates multiple data sources (shipment manifests, EU sanctions lists, ICAO/IMO transport data) to detect diversion risks, which is fundamentally a Read operation. Although it operates in a sensitive compliance domain (dual-use technology monitoring), it does not execute code, delete data, move money, or modify records—it only retrieves and analyzes data.
From the tool's definition Tool performs detection and cross-referencing of shipment manifests, sanctions lists, and transport data to 'identify suspicious transfers' and output 'risk assessment.' No modification of data, deletion, code execution, or financial transactions occur.
Risk signalsAccepts file system path (route.destination)
Attacks that exploit this kind of access
The rule that runs dual_use_tech_diversion_monitor 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_tech_diversion_monitor, this is the rule to start with:
dual_use_tech_diversion_monitor 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 Knowledge, apply this rule, and every dual_use_tech_diversion_monitor call is checked against it from then on.
Questions about dual_use_tech_diversion_monitor
Asynchronous T5-level tool for COO persona to detect unauthorized diversion of dual-use technologies. Cross-references shipment manifests, EU sanctions lists, and ICAO/IMO transport data to identify suspicious transfers. Inputs: shipment IDs, company identifiers, or geographic routes. Outputs structured diversion risk assessment with source provenance. Requires async:true to avoid 402 timeout. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
dual_use_tech_diversion_monitor accepts 5 parameters: async, route, companyId, shipmentId, techCategory. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for dual_use_tech_diversion_monitor: 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.
dual_use_tech_diversion_monitor 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 dual_use_tech_diversion_monitor 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 dual_use_tech_diversion_monitor. 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.
dual_use_tech_diversion_monitor 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.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue