wps_word_find_in_document
在Word文档中查找文本并返回位置信息，不执行替换操作。 使用场景： - "找一下'项目名称'在文档的哪个位置" - "看看文档里有哪些地方需要填写" - 在使用smart_fill_field之前，先用此工具定位关键字 返回信息包括：匹配文本、字符起止位置、所在段落索引、上下文（前后50字符）。 与find_replace不同，此工具仅查找不替换，返回位置信息供后续操作使用。
This record as markdown: /tools/wps-office-mcp/wps-word-find-in-document.md
What wps_word_find_in_document does on Wps Office
AI agents call wps_word_find_in_document to retrieve information from Wps Office 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 |
|---|---|---|---|
find_text | string | Yes | 要查找的文本 |
match_case | boolean | — | 是否区分大小写，默认false |
max_results | number | — | 最大返回结果数，默认20 |
match_whole_word | boolean | — | 是否全字匹配，默认false |
Parameters from the server's own tool schema.
Why wps_word_find_in_document is rated Low
Even though wps_word_find_in_document 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.
Attacks that exploit this kind of access
The rule that runs wps_word_find_in_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wps Office, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wps_word_find_in_document, this is the rule to start with:
wps_word_find_in_document 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 Wps Office, apply this rule, and every wps_word_find_in_document call is checked against it from then on.
Questions about wps_word_find_in_document
在Word文档中查找文本并返回位置信息，不执行替换操作。 使用场景： - "找一下'项目名称'在文档的哪个位置" - "看看文档里有哪些地方需要填写" - 在使用smart_fill_field之前，先用此工具定位关键字 返回信息包括：匹配文本、字符起止位置、所在段落索引、上下文（前后50字符）。 与find_replace不同，此工具仅查找不替换，返回位置信息供后续操作使用。. It is categorised as a Read tool in the Wps Office MCP Server, which means it retrieves data without modifying state.
wps_word_find_in_document accepts 4 parameters: find_text, match_case, max_results, match_whole_word. Required: find_text. The full parameter table on this page comes from the server's own tool schema.
Register the Wps Office MCP server in PolicyLayer and add a rule for wps_word_find_in_document: 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 Wps Office. Nothing to install.
wps_word_find_in_document 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 wps_word_find_in_document 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 wps_word_find_in_document. 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.
wps_word_find_in_document is provided by the Wps Office MCP server (wps-office-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wps Office, and thousands of servers like it.
This server
Across the catalogue