onloon-customer-dev__writeCandidate
统一写入/更新潜客 record + candidates/index.json(减少手拼路径错误)
This record as markdown: /tools/lxwl-mcp-server/onloon-customer-dev--writecandidate.md
What onloon-customer-dev__writeCandidate does on Lxwl
AI agents use onloon-customer-dev__writeCandidate 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 | — | 已有潜客 id;新建时不要乱编,交给脚本生成 |
file | string | — | |
merge | boolean | — | |
domain | string | — | |
emails | array | — | |
website | string | — | |
contacts | array | — | 联系人数组 |
dedupeKey | string | — | |
sessionDir | string | — | |
companyName | string | — | |
countryCode | string | — | |
sourceChannel | string | — |
Parameters from the server's own tool schema.
Why onloon-customer-dev__writeCandidate is rated Medium
An AI agent can call onloon-customer-dev__writeCandidate 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 signalsAccepts file system path (file) · High parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs onloon-customer-dev__writeCandidate 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__writeCandidate, this is the rule to start with:
onloon-customer-dev__writeCandidate 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__writeCandidate call is checked against it from then on.
Questions about onloon-customer-dev__writeCandidate
统一写入/更新潜客 record + candidates/index.json(减少手拼路径错误). 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__writeCandidate accepts 12 parameters: id, file, merge, domain, emails, website, contacts, dedupeKey, sessionDir, companyName, countryCode, sourceChannel. 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__writeCandidate: 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__writeCandidate 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__writeCandidate 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__writeCandidate. 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__writeCandidate 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