onloon-social-chat__searchMessages
Inbox 聊天记录搜索（Search 弹窗 — 聊天记录 Tab）
This record as markdown: /tools/lxwl-mcp-server/onloon-social-chat--searchmessages.md
What onloon-social-chat__searchMessages does on Lxwl
AI agents call onloon-social-chat__searchMessages 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 |
|---|---|---|---|
page | integer | — | |
size | integer | — | |
scope | string | — | |
pageId | string | — | |
dateEnd | string | — | |
keyword | string | — | |
fbUserId | string | — | |
platform | integer | — | |
dateBegin | string | — | |
searchType | string | — | 0=全部消息，1=文档，2=链接，3=联系方式，4=图片/视频，5=标注。 |
queryUserId | string | — | |
participantId | string | — |
Parameters from the server's own tool schema.
Why onloon-social-chat__searchMessages is rated Low
Even though onloon-social-chat__searchMessages 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 (14 properties)
Attacks that exploit this kind of access
The rule that runs onloon-social-chat__searchMessages 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-social-chat__searchMessages, this is the rule to start with:
onloon-social-chat__searchMessages 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-social-chat__searchMessages call is checked against it from then on.
Questions about onloon-social-chat__searchMessages
Inbox 聊天记录搜索（Search 弹窗 — 聊天记录 Tab）. It is categorised as a Read tool in the Lxwl MCP Server, which means it retrieves data without modifying state.
onloon-social-chat__searchMessages accepts 12 parameters: page, size, scope, pageId, dateEnd, keyword, fbUserId, platform, dateBegin, searchType, queryUserId, participantId. 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-social-chat__searchMessages: 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-social-chat__searchMessages 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-social-chat__searchMessages 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-social-chat__searchMessages. 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-social-chat__searchMessages 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