AI agents call search_text to retrieve information from Docx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve or query data without side effects. Given the empty description, confidence is slightly reduced, but the tool name and server context strongly suggest a read-only search capability. Sibling tools show both read operations (accept_all_changes, accept_change) and write operations (add_comment, add_bookmark), but 'search_text' aligns with the read category based on nomenclature.
From the tool's definition Tool named 'search_text' on a document server designed for 'reading, editing, and validating Microsoft Word documents.' The name and server context indicate text search/query functionality with no data modification.
Documented attack patterns abuse exactly the kind of access search_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for search_text:
{
"version": "1",
"default": "deny",
"tools": {
"search_text": {}
}
}search_text is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_text. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.
Register the Docx MCP server in PolicyLayer and add a rule for search_text: 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 Docx. Nothing to install.
search_text 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 search_text 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 search_text. 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.
search_text is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.