onloon-crm-customer-management__runScene

运行客户场景（POST /bshop/contacts/company/v3/list + sceneId）

SERVERLxwl SOURCE@lxwl/mcp-server

High RISK CLASS

Category Execute

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lxwl-mcp-server/onloon-crm-customer-management--runscene.md

WHAT IT DOES

What onloon-crm-customer-management__runScene does on Lxwl

AI agents invoke onloon-crm-customer-management__runScene to trigger actions in Lxwl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`page`	integer	—
`pool`	string	—	mine=私海，public=公海，shared=共享池。
`size`	integer	—
`sceneId`	string	—
`pageSize`	string	—
`sharedScope`	string	—	pool=shared 时：toMe=共享给我，fromMe=我共享出去。
`previewLimit`	string	—

Parameters from the server's own tool schema.

RISK

Why onloon-crm-customer-management__runScene is rated High

onloon-crm-customer-management__runScene triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs onloon-crm-customer-management__runScene 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__runScene, this is the rule to start with:

onloon-crm-customer-management__runScene Rate-limited

onloon-crm-customer-management__runScene stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "onloon-crm-customer-management__runScene": {
      "limits": [
        {
          "counter": "onloon-crm-customer-management__runscene_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-crm-customer-management__runScene call is checked against it from then on.

FAQ

Questions about onloon-crm-customer-management__runScene

What does the onloon-crm-customer-management__runScene tool do? +

运行客户场景（POST /bshop/contacts/company/v3/list + sceneId）. It is categorised as a Execute tool in the Lxwl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does onloon-crm-customer-management__runScene accept? +

onloon-crm-customer-management__runScene accepts 7 parameters: page, pool, size, sceneId, pageSize, sharedScope, previewLimit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on onloon-crm-customer-management__runScene? +

Register the Lxwl MCP server in PolicyLayer and add a rule for onloon-crm-customer-management__runScene: 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.

What risk level is onloon-crm-customer-management__runScene? +

onloon-crm-customer-management__runScene is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit onloon-crm-customer-management__runScene? +

Yes. Add a rate_limit block to the onloon-crm-customer-management__runScene 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 onloon-crm-customer-management__runScene completely? +

Set action: deny in the PolicyLayer policy for onloon-crm-customer-management__runScene. 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 onloon-crm-customer-management__runScene? +

onloon-crm-customer-management__runScene 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.

KEEP EXPLORING

More on Lxwl, and thousands of servers like it.

This server

All 236 Lxwl tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →