AI agents call customs_query_declaration_list 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/queries existing customs declaration data without modifying, deleting, executing code, or committing financial transactions. It has no documented side effects and follows standard read semantics for querying list data. Blast radius is minimal as it only exposes existing declaration information that a user would need permission to access anyway.
From the tool's definition Tool name uses 'query' verb and description indicates it queries/retrieves customs declaration lists by status groups.
Attacks that exploit this kind of access
Query customs declaration list by status semantic groups (e.g. 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_declaration_list: 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_declaration_list 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_declaration_list 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_declaration_list. 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_declaration_list 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 →