customs_submit_ai_maker · Customs MCP: Risk & Policy

WHAT IT DOES

What customs_submit_ai_maker does on Customs

AI agents use customs_submit_ai_maker to create or update resources in Customs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Customs environment.

WHY IT NEEDS A POLICY

Why customs_submit_ai_maker needs a policy

This is a Write operation because it creates/submits formal customs declarations, which are reversible administrative records. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). However, severity is high because submitting false or malicious customs declarations could constitute fraud, create legal liability, and disrupt trade operations.

From the tool's definition Tool name contains 'submit' and description states 'Submit declaration source documents'. The tool creates or modifies declarations by submitting official customs documentation (invoice, packing list, contract) into a regulatory system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

customs_submit_ai_maker Rate-limited

customs_submit_ai_maker stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "customs_submit_ai_maker": {
      "limits": [
        {
          "counter": "customs_submit_ai_maker_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Customs, so you can run agents against it safely.

FAQ

Questions about customs_submit_ai_maker

What does the customs_submit_ai_maker tool do? +

Submit declaration source documents (invoice, packing list, contract,. It is categorised as a Write tool in the Customs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on customs_submit_ai_maker? +

Register the Customs MCP server in PolicyLayer and add a rule for customs_submit_ai_maker: 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.

What risk level is customs_submit_ai_maker? +

customs_submit_ai_maker is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit customs_submit_ai_maker? +

Yes. Add a rate_limit block to the customs_submit_ai_maker 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.

How do I block customs_submit_ai_maker completely? +

Set action: deny in the PolicyLayer policy for customs_submit_ai_maker. 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.

What MCP server provides customs_submit_ai_maker? +

customs_submit_ai_maker 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.