AI agents call customs_get_declaration_status 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 queries and retrieves the status of an existing customs declaration without modifying, creating, executing operations on external systems, or deleting any data. It is a straightforward read operation on declaration data, presenting minimal risk if misused by an AI agent—at worst, it could expose non-sensitive filing status information already intended for authorized users.
From the tool's definition Tool name 'customs_get_declaration_status' and description 'Query the current filing status of a customs declaration' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Query the current filing status of a customs declaration by. 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_status: 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_status 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_status 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_status. 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_status 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 →