xpath_query

Run XPath against any DOCX part. Pre-bound namespaces: w, w14, r, wp, a, mc.

SERVERDocx SOURCEsecurityronin/docx-mcp

High RISK CLASS

Category Execute

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/xpath-query.md

WHAT IT DOES

What xpath_query does on Docx

AI agents invoke xpath_query to trigger actions in Docx. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why xpath_query is rated High

This tool executes arbitrary XPath queries against DOCX document parts. While XPath is primarily a query language, executing arbitrary expressions against any part of the document structure constitutes an Execute-level action. The 'any DOCX part' scope and pre-bound namespaces suggest broad access to internal XML structures.

From the tool's definition "Run XPath against any DOCX part" — executes arbitrary XPath expressions against document internals

Attacks that exploit this kind of access

RECOMMENDED RULE

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

xpath_query Rate-limited

xpath_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "xpath_query": {
      "limits": [
        {
          "counter": "xpath_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about xpath_query

What does the xpath_query tool do? +

Run XPath against any DOCX part. Pre-bound namespaces: w, w14, r, wp, a, mc. It is categorised as a Execute tool in the Docx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xpath_query? +

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

xpath_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit xpath_query? +

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

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

xpath_query 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 → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →