onloon-crm-customer-management__filterCompanies
高级筛选客户（POST /bshop/contacts/company/v3/list + sceneFilter）
This record as markdown: /tools/lxwl-mcp-server/onloon-crm-customer-management--filtercompanies.md
What onloon-crm-customer-management__filterCompanies does on Lxwl
AI agents call onloon-crm-customer-management__filterCompanies 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 |
|---|---|---|---|
page | integer | — | |
pool | string | — | mine=私海，public=公海，shared=共享池。 |
size | integer | — | |
query | object | — | 客户 sceneFilter 全量字段。禁止 personHas*，用 companyHasWhatsapp/companyHasPerson。禁止 lastFollowupAt/behaviors[]。source 用 code。tagIds 必须是客户标签。 |
stage | string | — | |
source | string | — | |
country | string | — | |
keyword | string | — | |
pageSize | string | — | |
companyInfo | string | — | |
sharedScope | string | — | pool=shared 时：toMe=共享给我，fromMe=我共享出去。 |
previewLimit | string | — |
Parameters from the server's own tool schema.
Why onloon-crm-customer-management__filterCompanies is rated Low
Even though onloon-crm-customer-management__filterCompanies 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.
Risk signalsHigh parameter count (200 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-customer-management__filterCompanies 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__filterCompanies, this is the rule to start with:
onloon-crm-customer-management__filterCompanies 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-crm-customer-management__filterCompanies call is checked against it from then on.
Questions about onloon-crm-customer-management__filterCompanies
高级筛选客户（POST /bshop/contacts/company/v3/list + sceneFilter）. It is categorised as a Read tool in the Lxwl MCP Server, which means it retrieves data without modifying state.
onloon-crm-customer-management__filterCompanies accepts 12 parameters: page, pool, size, query, stage, source, country, keyword, pageSize, companyInfo, sharedScope, previewLimit. 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__filterCompanies: 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__filterCompanies 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-crm-customer-management__filterCompanies 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__filterCompanies. 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__filterCompanies 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