search_text

A read tool on the Docx MCP server.

SERVERDocx SOURCEsecurityronin/docx-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/search-text.md

WHAT IT DOES

What search_text does on Docx

AI agents call search_text to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_text is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_text safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_text, this is the rule to start with:

search_text Allowed

search_text is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_text": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every search_text call is checked against it from then on.

FAQ

Questions about search_text

What does the search_text tool do? +

search_text is a read tool on the Docx MCP server. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_text? +

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.

What risk level is search_text? +

search_text is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_text? +

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.

How do I block search_text completely? +

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.

What MCP server provides search_text? +

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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →