onloon-crm-customer-management__saveScene
保存客户筛选场景（sceneType=company）
This record as markdown: /tools/lxwl-mcp-server/onloon-crm-customer-management--savescene.md
What onloon-crm-customer-management__saveScene does on Lxwl
AI agents use onloon-crm-customer-management__saveScene 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 |
|---|---|---|---|
id | string | — | |
name | string | — | |
pool | string | — | mine=私海，public=公海，shared=共享池。 |
query | object | — | 客户 sceneFilter 全量字段。禁止 personHas*，用 companyHasWhatsapp/companyHasPerson。禁止 lastFollowupAt/behaviors[]。source 用 code。tagIds 必须是客户标签。 |
stage | string | — | |
sceneId | string | — | |
confirmed | boolean | — | 用户明确同意后再传 true |
sceneType | string | — | 客户包固定 company；传 person/contact 会报错。 |
Parameters from the server's own tool schema.
Why onloon-crm-customer-management__saveScene is rated Medium
An AI agent can call onloon-crm-customer-management__saveScene 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 (195 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-customer-management__saveScene 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__saveScene, this is the rule to start with:
onloon-crm-customer-management__saveScene 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-customer-management__saveScene call is checked against it from then on.
Questions about onloon-crm-customer-management__saveScene
保存客户筛选场景（sceneType=company）. 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-customer-management__saveScene accepts 8 parameters: id, name, pool, query, stage, sceneId, confirmed, sceneType. 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__saveScene: 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__saveScene 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-customer-management__saveScene 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__saveScene. 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__saveScene 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