onloon-customer-dev-b2c__buildSearchQuery
客户开发-B2C平台(混合)· 构建 Google 查询串(对齐 digger getSearchLineBySc)
This record as markdown: /tools/lxwl-mcp-server/onloon-customer-dev-b2c--buildsearchquery.md
What onloon-customer-dev-b2c__buildSearchQuery does on Lxwl
AI agents invoke onloon-customer-dev-b2c__buildSearchQuery 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 |
|---|---|---|---|
country | string | — | |
keyword | string | — | |
website | string | — |
Parameters from the server's own tool schema.
Why onloon-customer-dev-b2c__buildSearchQuery is rated High
onloon-customer-dev-b2c__buildSearchQuery 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
The rule that runs onloon-customer-dev-b2c__buildSearchQuery 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-customer-dev-b2c__buildSearchQuery, this is the rule to start with:
onloon-customer-dev-b2c__buildSearchQuery 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-customer-dev-b2c__buildSearchQuery call is checked against it from then on.
Questions about onloon-customer-dev-b2c__buildSearchQuery
客户开发-B2C平台(混合)· 构建 Google 查询串(对齐 digger getSearchLineBySc). 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.
onloon-customer-dev-b2c__buildSearchQuery accepts 3 parameters: country, keyword, website. 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-customer-dev-b2c__buildSearchQuery: 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-customer-dev-b2c__buildSearchQuery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the onloon-customer-dev-b2c__buildSearchQuery 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-customer-dev-b2c__buildSearchQuery. 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-customer-dev-b2c__buildSearchQuery 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