onloon-crm-order__createOrder
创建订单(配置单据) POST /bshop/contacts/order/save type=order。buyer/seller 的 companyName、contactsName、mail 后端必填且必须真实,禁止编造;先 getTradeInfo。
This record as markdown: /tools/lxwl-mcp-server/onloon-crm-order--createorder.md
What onloon-crm-order__createOrder does on Lxwl
AI agents use onloon-crm-order__createOrder to create or update resources in Lxwl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lxwl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cost | object | — | 价格条款/付款 |
date | string | — | 单据日期,格式 yyyy-MM-dd |
fees | array | — | |
name | string | — | 单据名称,最长 50 个字符,且必须唯一。超长请缩短或把说明放到 remark |
rate | string | — | 汇率,不填则按 currencyCode 查表 |
buyer | object | — | 贸易信息,后端必填且必须真实,禁止编造;先 getTradeInfo。其余键仅允许 getTradeInfo 返回的真实字段,禁止编造邮箱/公司名。其余键仅允许 getTradeInfo 返回的真实字段,禁止编造邮箱/公司名 |
remark | string | — | |
seller | object | — | 贸易信息,后端必填且必须真实,禁止编造;先 getTradeInfo。其余键仅允许 getTradeInfo 返回的真实字段,禁止编造邮箱/公司名。其余键仅允许 getTradeInfo 返回的真实字段,禁止编造邮箱/公司名 |
status | string | — | 0草稿 3已下单 7待采购 8采购中 9采购完成 10待生产 11生产中 12生产完成 13库存调货完成 14出运完成 15待收款 16部分收款 17收款完成 18已完成 19已作废 |
freight | object | — | 货运信息 |
folderId | string | — | |
products | array | — |
Parameters from the server's own tool schema.
Why onloon-crm-order__createOrder is rated Medium
An AI agent can call onloon-crm-order__createOrder faster than any human can review: one bad instruction and it creates or modifies resources in Lxwl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (86 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-order__createOrder 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-crm-order__createOrder, this is the rule to start with:
onloon-crm-order__createOrder 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-crm-order__createOrder call is checked against it from then on.
Questions about onloon-crm-order__createOrder
创建订单(配置单据) POST /bshop/contacts/order/save type=order。buyer/seller 的 companyName、contactsName、mail 后端必填且必须真实,禁止编造;先 getTradeInfo。. It is categorised as a Write tool in the Lxwl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
onloon-crm-order__createOrder accepts 12 parameters: cost, date, fees, name, rate, buyer, remark, seller, status, freight, folderId, products. 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-crm-order__createOrder: 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-crm-order__createOrder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the onloon-crm-order__createOrder 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-crm-order__createOrder. 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-crm-order__createOrder 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