sanitize_metadata

A write tool on the Docx MCP server.

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/sanitize-metadata.md

WHAT IT DOES

What sanitize_metadata does on Docx

AI agents use sanitize_metadata to create or update resources in Docx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.

RISK

Why sanitize_metadata is rated Medium

Sanitizing metadata modifies document properties reversibly (author, timestamps, custom fields, etc.) without deletion or financial impact. While the empty description reduces confidence slightly, the context of a document editing MCP server and the action verb 'sanitize' (implying data transformation) places this firmly in Write rather than Read or Destructive.

From the tool's definition Tool name 'sanitize_metadata' on a document editing server implies modification of document metadata; server description emphasizes 'editing...Microsoft Word documents' and 'OOXML-level document manipulation'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sanitize_metadata Rate-limited

sanitize_metadata stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sanitize_metadata": {
      "limits": [
        {
          "counter": "sanitize_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sanitize_metadata

What does the sanitize_metadata tool do? +

sanitize_metadata is a write tool on the Docx MCP server. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sanitize_metadata? +

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

sanitize_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sanitize_metadata? +

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

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

sanitize_metadata 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

Govern customer-ops agents →Argument validation →Scoped token →