onloon-customer-dev-marketing__submitMarketingTask
自动开发营销 · 一次提交四步（createTask + editTask×3）。四段均必填：excavate / develop / sop / archive。必须 confirmed=true。
This record as markdown: /tools/lxwl-mcp-server/onloon-customer-dev-marketing--submitmarketingtask.md
What onloon-customer-dev-marketing__submitMarketingTask does on Lxwl
AI agents use onloon-customer-dev-marketing__submitMarketingTask 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 |
|---|---|---|---|
sop | object | Yes | Step2 SOP。已知字段外会原样提交后端，只用示例里出现过的键，禁止乱猜 |
archive | object | Yes | Step3 建档。已知字段外会原样提交后端，只用示例里出现过的键，禁止乱猜 |
develop | object | Yes | Step1。已知字段：marketingWays、mailMarketing*、whatsappMarketing*。edit-task 会把其余键原样提交后端，禁止乱猜未出现在示例里的字段。已知字段外会原样提交后端，只用示例里出现过的键，禁止乱猜 |
excavate | object | Yes | Step0 挖掘条件。含 ins_search 时 filterTags 必填。 |
confirmed | boolean | — | 用户明确同意后再传 true |
Parameters from the server's own tool schema.
Why onloon-customer-dev-marketing__submitMarketingTask is rated Medium
An AI agent can call onloon-customer-dev-marketing__submitMarketingTask 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 (35 properties)
Attacks that exploit this kind of access
The rule that runs onloon-customer-dev-marketing__submitMarketingTask 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__submitMarketingTask, this is the rule to start with:
onloon-customer-dev-marketing__submitMarketingTask 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__submitMarketingTask call is checked against it from then on.
Questions about onloon-customer-dev-marketing__submitMarketingTask
自动开发营销 · 一次提交四步（createTask + editTask×3）。四段均必填：excavate / develop / sop / archive。必须 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__submitMarketingTask accepts 5 parameters: sop, archive, develop, excavate, confirmed. Required: sop, archive, develop, excavate. 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__submitMarketingTask: 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__submitMarketingTask 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__submitMarketingTask 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__submitMarketingTask. 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__submitMarketingTask 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