read_docx_text

Extract text from a local DOCX (Office OpenXML) file. Deterministic, no network.

SERVERNodebench SOURCEnodebench-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/io-github-homenshum-nodebench/read-docx-text.md

WHAT IT DOES

What read_docx_text does on Nodebench

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

RISK

Why read_docx_text is rated Low

This tool retrieves and extracts text content from an existing local file without modifying, deleting, executing code, or triggering external operations. It is a straightforward read operation with minimal risk even if misused by an AI agent—the worst outcome would be disclosure of file contents the agent already has local access to.

From the tool's definition Tool name 'read_docx_text' and description 'Extract text from a local DOCX file' indicate retrieval of data with no side effects. The explicit statement 'Deterministic, no network' confirms purely observational behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_docx_text safely

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

read_docx_text Allowed

read_docx_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": {
    "read_docx_text": {}
  }
}

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

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

FAQ

Questions about read_docx_text

What does the read_docx_text tool do? +

Extract text from a local DOCX (Office OpenXML) file. Deterministic, no network. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_docx_text? +

Register the Nodebench MCP server in PolicyLayer and add a rule for read_docx_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 Nodebench. Nothing to install.

What risk level is read_docx_text? +

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

Can I rate-limit read_docx_text? +

Yes. Add a rate_limit block to the read_docx_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 read_docx_text completely? +

Set action: deny in the PolicyLayer policy for read_docx_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 read_docx_text? +

read_docx_text is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

claude_read_file on Claude Bridge →browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

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