list_fields
List all fields in the document with their codes and cached values.
This record as markdown: /tools/securityronin-docx-mcp/list-fields.md
What list_fields does on Docx
AI agents call list_fields 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.
Why list_fields is rated Low
This tool queries and returns information about document fields without creating, modifying, deleting, or executing any operations. It is a pure read operation that retrieves structured metadata from a Word document. The low severity reflects that field enumeration poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'list_fields' and description states it 'List[s] all fields in the document with their codes and cached values' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_fields 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 list_fields, this is the rule to start with:
list_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every list_fields call is checked against it from then on.
Questions about list_fields
List all fields in the document with their codes and cached values. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.
Register the Docx MCP server in PolicyLayer and add a rule for list_fields: 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.
list_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_fields 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.
Set action: deny in the PolicyLayer policy for list_fields. 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.
list_fields 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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue