onloon-crm-customer-management__transferCustomerPool
客户池流转(transferCustomerPool)
This record as markdown: /tools/lxwl-mcp-server/onloon-crm-customer-management--transfercustomerpool.md
What onloon-crm-customer-management__transferCustomerPool does on Lxwl
AI agents use onloon-crm-customer-management__transferCustomerPool to commit financial operations through Lxwl, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | string | — | |
action | string | — | 池流转:认领/分配/释放公海/共享/取消共享/拒绝共享。 |
reason | string | — | |
companyId | string | — | |
confirmed | boolean | — | 用户明确同意后再传 true |
companyIds | string | — | |
accumulation | boolean | — | |
enjoyUserIds | string | — | |
targetUserId | string | — | |
assignedUserId | string | — |
Parameters from the server's own tool schema.
Why onloon-crm-customer-management__transferCustomerPool is rated Critical
onloon-crm-customer-management__transferCustomerPool moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-customer-management__transferCustomerPool 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-customer-management__transferCustomerPool, this is the rule to start with:
Any call to onloon-crm-customer-management__transferCustomerPool is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-crm-customer-management__transferCustomerPool call is checked against it from then on.
Questions about onloon-crm-customer-management__transferCustomerPool
客户池流转(transferCustomerPool). It is categorised as a Financial tool in the Lxwl MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
onloon-crm-customer-management__transferCustomerPool accepts 10 parameters: ids, action, reason, companyId, confirmed, companyIds, accumulation, enjoyUserIds, targetUserId, assignedUserId. 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-customer-management__transferCustomerPool: 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-customer-management__transferCustomerPool is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the onloon-crm-customer-management__transferCustomerPool 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-customer-management__transferCustomerPool. 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-customer-management__transferCustomerPool 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.
Across the catalogue