onloon-explore-customs-data__getMerchantTradeProfile
customs.getMerchantTradeProfile — 海关公司贸易画像
This record as markdown: /tools/lxwl-mcp-server/onloon-explore-customs-data--getmerchanttradeprofile.md
What onloon-explore-customs-data__getMerchantTradeProfile does on Lxwl
AI agents call onloon-explore-customs-data__getMerchantTradeProfile to retrieve information from Lxwl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sections | array | — | summary=概要，partners=伙伴，countries=国家，products=产品，annual=年度，graph=贸易圈。 |
merchantId | string | — | |
companyName | string | — | |
countryCode | string | — | |
tradeDirection | string | — | buyer=进口/采购视角，supply=出口/供应视角，both=双向。脚本不接受 import/export。 |
Parameters from the server's own tool schema.
Why onloon-explore-customs-data__getMerchantTradeProfile is rated Low
Even though onloon-explore-customs-data__getMerchantTradeProfile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs onloon-explore-customs-data__getMerchantTradeProfile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lxwl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For onloon-explore-customs-data__getMerchantTradeProfile, this is the rule to start with:
onloon-explore-customs-data__getMerchantTradeProfile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-explore-customs-data__getMerchantTradeProfile call is checked against it from then on.
Questions about onloon-explore-customs-data__getMerchantTradeProfile
customs.getMerchantTradeProfile — 海关公司贸易画像. It is categorised as a Read tool in the Lxwl MCP Server, which means it retrieves data without modifying state.
onloon-explore-customs-data__getMerchantTradeProfile accepts 5 parameters: sections, merchantId, companyName, countryCode, tradeDirection. The full parameter table on this page comes from the server's own tool schema.
Register the Lxwl MCP server in PolicyLayer and add a rule for onloon-explore-customs-data__getMerchantTradeProfile: 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 Lxwl. Nothing to install.
onloon-explore-customs-data__getMerchantTradeProfile 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 onloon-explore-customs-data__getMerchantTradeProfile 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 onloon-explore-customs-data__getMerchantTradeProfile. 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.
onloon-explore-customs-data__getMerchantTradeProfile is provided by the Lxwl MCP server (@lxwl/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lxwl, and thousands of servers like it.
This server
Across the catalogue