read_docx
Read and extract text content from a Word document.
This record as markdown: /tools/andrew82106-llm-docx-agent-mcp/read-docx.md
What read_docx does on Docx
AI agents call read_docx 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.
Why read_docx is rated Low
This tool retrieves data from an existing Word document without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk of misuse.
From the tool's definition Tool name 'read_docx' and description 'Read and extract text content from a Word document' explicitly indicate retrieval of document content with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs read_docx 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 read_docx, this is the rule to start with:
read_docx 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 Docx, apply this rule, and every read_docx call is checked against it from then on.
Questions about read_docx
Read and extract text content from a Word document. 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 read_docx: 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.
read_docx 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 read_docx 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 read_docx. 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.
read_docx is provided by the Docx MCP server (andrew82106/llm_docx_agent_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
This server
Across the catalogue