onloon-customer-dev-marketing__createTask
自动开发营销 · Step0 创建(POST /bshop/centra/customerdev/createTask)。必须 confirmed=true。
This record as markdown: /tools/lxwl-mcp-server/onloon-customer-dev-marketing--createtask.md
What onloon-customer-dev-marketing__createTask does on Lxwl
AI agents use onloon-customer-dev-marketing__createTask 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 | — | |
step | string | — | |
keyword | string | — | |
sources | string | — | |
confirmed | boolean | — | 用户明确同意后再传 true |
countries | string | — | |
buyerNames | string | — | |
filterTags | string | — | JSON 数组字符串,含 ins_search 必填。推荐改走 submitMarketingTask.excavate.filterTags[] |
countryType | string | — | |
excludeMails | string | — | JSON 数组字符串,如 ["a@x.com"] |
filterSources | array | — | google_search=全球引擎,enterprise_data=企业数据,fb_search=Facebook,ins_search=Instagram,whatsapp_search=WhatsApp,tiktok_search=TikTok,custom_create=海关数据,canton_fair=广交会 |
Parameters from the server's own tool schema.
Why onloon-customer-dev-marketing__createTask is rated Medium
An AI agent can call onloon-customer-dev-marketing__createTask 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 (25 properties)
Attacks that exploit this kind of access
The rule that runs onloon-customer-dev-marketing__createTask 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-marketing__createTask, this is the rule to start with:
onloon-customer-dev-marketing__createTask 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-customer-dev-marketing__createTask call is checked against it from then on.
Questions about onloon-customer-dev-marketing__createTask
自动开发营销 · Step0 创建(POST /bshop/centra/customerdev/createTask)。必须 confirmed=true。. 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-customer-dev-marketing__createTask accepts 12 parameters: id, name, step, keyword, sources, confirmed, countries, buyerNames, filterTags, countryType, excludeMails, filterSources. 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-marketing__createTask: 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-marketing__createTask 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-customer-dev-marketing__createTask 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-marketing__createTask. 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-marketing__createTask 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