New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

onloon-customer-dev-b2c__buildSearchQuery

客户开发-B2C平台(混合)· 构建 Google 查询串(对齐 digger getSearchLineBySc)

SERVERLxwl SOURCE@lxwl/mcp-server
High RISK CLASS
Category Execute
Parameters 30 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-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.

ParameterTypeRequiredDescription
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.

Questions about onloon-customer-dev-b2c__buildSearchQuery

What does the onloon-customer-dev-b2c__buildSearchQuery tool do? +

客户开发-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.

What parameters does onloon-customer-dev-b2c__buildSearchQuery accept? +

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.

How do I enforce a policy on onloon-customer-dev-b2c__buildSearchQuery? +

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.

What risk level is onloon-customer-dev-b2c__buildSearchQuery? +

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

Can I rate-limit onloon-customer-dev-b2c__buildSearchQuery? +

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.

How do I block onloon-customer-dev-b2c__buildSearchQuery completely? +

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.

What MCP server provides onloon-customer-dev-b2c__buildSearchQuery? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Lxwl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.