onloon-crm-customer-management__updateContact
薄包装联系人更新。字段与 onloon-crm-contact updateContact 相同。社媒/职位/办公电话走 patch,禁止只改 remark。
This record as markdown: /tools/lxwl-mcp-server/onloon-crm-customer-management--updatecontact.md
What onloon-crm-customer-management__updateContact does on Lxwl
AI agents use onloon-crm-customer-management__updateContact 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 | — | |
email | string | — | |
patch | object | — | 部分更新。至少包含一个可更新字段。 |
phone | string | — | |
stage | string | — | |
remark | string | — | 备注。只放说明文字,禁止放 WhatsApp/职位/社媒 URL |
confirmed | boolean | Yes | 用户明确同意后再传 true |
contactId | string | — |
Parameters from the server's own tool schema.
Why onloon-crm-customer-management__updateContact is rated Medium
An AI agent can call onloon-crm-customer-management__updateContact 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 URL/endpoint input (patch.socialAccounts[].url) · High parameter count (48 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-customer-management__updateContact 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-crm-customer-management__updateContact, this is the rule to start with:
onloon-crm-customer-management__updateContact 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-crm-customer-management__updateContact call is checked against it from then on.
Questions about onloon-crm-customer-management__updateContact
薄包装联系人更新。字段与 onloon-crm-contact updateContact 相同。社媒/职位/办公电话走 patch,禁止只改 remark。. 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-crm-customer-management__updateContact accepts 9 parameters: id, name, email, patch, phone, stage, remark, confirmed, contactId. Required: confirmed. 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-crm-customer-management__updateContact: 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-crm-customer-management__updateContact 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-crm-customer-management__updateContact 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-crm-customer-management__updateContact. 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-crm-customer-management__updateContact 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