AI agents call customs_query_dual_use_item to retrieve information from Customs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only query against a reference database (dual-use/export-control catalog). Screening a product means checking its status against regulatory lists, which is a data retrieval operation with no side effects. No data is created, modified, deleted, or financial obligations incurred. The tool merely informs the user whether a product matches export-control criteria.
From the tool's definition Tool name contains 'query' and description states 'Screen a product against the dual-use / export-control catalog' — this is a lookup/screening operation that retrieves information from a catalog without modifying data or triggering external actions.
Attacks that exploit this kind of access
Screen a product against the dual-use / export-control catalog. It is categorised as a Read tool in the Customs MCP Server, which means it retrieves data without modifying state.
Register the Customs MCP server in PolicyLayer and add a rule for customs_query_dual_use_item: 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 Customs. Nothing to install.
customs_query_dual_use_item 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 customs_query_dual_use_item 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 customs_query_dual_use_item. 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.
customs_query_dual_use_item is provided by the Customs MCP server (yak33/customs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →