Low Risk

extract_local_document_structure

【本地文档结构提取工具】从本地文件路径解析.docx文件结构

How to control extract_local_document_structure ↓

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

Low Risk

This tool retrieves and analyzes the structure of an existing Word document. It performs a read-only operation that queries the document's composition (tables, headings, paragraphs, etc.) without creating, modifying, deleting, or executing any code. The worst-case misuse is information disclosure of document contents, which is low-severity.

From the tool's definition Tool name 'extract_local_document_structure' and description indicate parsing and analyzing document structure from a local .docx file. Keywords: 'extract', 'parse', 'structure' — purely data retrieval with no modification or execution.

Documented attack patterns abuse exactly the kind of access extract_local_document_structure gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_local_document_structure:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_local_document_structure": {}
  }
}

extract_local_document_structure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docx_MCP_cj — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the extract_local_document_structure tool do? +

【本地文档结构提取工具】从本地文件路径解析.docx文件结构. It is categorised as a Read tool in the Docx_MCP_cj MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract_local_document_structure? +

Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for extract_local_document_structure: 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_MCP_cj. Nothing to install.

What risk level is extract_local_document_structure? +

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

Can I rate-limit extract_local_document_structure? +

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

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

extract_local_document_structure is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx_MCP_cj tool call.

Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.