audit_document

Run a comprehensive structural audit of the document.

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/audit-document.md

WHAT IT DOES

What audit_document does on Docx

AI agents call audit_document 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 audit_document is rated Low

An audit operation reads and analyzes document structure without modifying, deleting, or executing anything. It is a read-only inspection operation that reports on document properties and structure.

From the tool's definition "Run a comprehensive structural audit of the document"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audit_document 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 audit_document, this is the rule to start with:

audit_document Allowed

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

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 audit_document call is checked against it from then on.

FAQ

Questions about audit_document

What does the audit_document tool do? +

Run a comprehensive structural audit of the document. 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 audit_document? +

Register the Docx MCP server in PolicyLayer and add a rule for audit_document: 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 audit_document? +

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

Can I rate-limit audit_document? +

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

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

audit_document 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

The MCP Attack Database →

Guides

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