This record as markdown: /tools/lxwl-mcp-server/onloon-crm-contact--listauditevents.md
What onloon-crm-contact__listAuditEvents does on Lxwl
AI agents call onloon-crm-contact__listAuditEvents to retrieve information from Lxwl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | |
userId | string | — | |
contactId | string | — | |
dateRange | object | — | 时间范围。{type:lastDays,days:7} 或 {timeType:last_day_30} 或 {start,end}/{startTime,endTime} |
eventType | string | — |
Parameters from the server's own tool schema.
Why onloon-crm-contact__listAuditEvents is rated Low
Even though onloon-crm-contact__listAuditEvents only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs onloon-crm-contact__listAuditEvents 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-contact__listAuditEvents, this is the rule to start with:
onloon-crm-contact__listAuditEvents is read-only, so it stays allowed. 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-contact__listAuditEvents call is checked against it from then on.
Questions about onloon-crm-contact__listAuditEvents
联系人操作历史。. It is categorised as a Read tool in the Lxwl MCP Server, which means it retrieves data without modifying state.
onloon-crm-contact__listAuditEvents accepts 5 parameters: id, userId, contactId, dateRange, eventType. 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-contact__listAuditEvents: 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-contact__listAuditEvents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the onloon-crm-contact__listAuditEvents 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-contact__listAuditEvents. 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-contact__listAuditEvents 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