AI agents call customs_get_declaration_detail 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.
This tool retrieves customs declaration records for inspection. While it accesses sensitive regulatory and trade data (potentially including shipment details, importer/exporter identities, and cargo information), the operation is read-only and causes no side effects. Severity is medium rather than low because misuse could expose sensitive trade/regulatory data, but no data is modified or deleted.
From the tool's definition Tool name 'customs_get_declaration_detail' and description 'Get the full declaration record' indicate a retrieval operation with no mutation.
Attacks that exploit this kind of access
Get the full declaration record (header / body / containers /. 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_get_declaration_detail: 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_get_declaration_detail 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_get_declaration_detail 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_get_declaration_detail. 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_get_declaration_detail 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 →