Low Risk

extract_fillable_fields

extract_fillable_fields

How to control extract_fillable_fields ↓

AI agents call extract_fillable_fields 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

The name pattern 'extract_*' is consistently used for read-only operations. No description provided, which lowers confidence slightly, but the semantic context of 'extract' combined with 'fillable_fields' strongly suggests introspection/querying of document state.

From the tool's definition Tool name 'extract_fillable_fields' indicates data retrieval with no modifying intent. The context describes analyzing Word documents and filling tables, suggesting this tool queries document structure to identify fields rather than modifying them.

Documented attack patterns abuse exactly the kind of access extract_fillable_fields 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_fillable_fields:

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

extract_fillable_fields 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_fillable_fields tool do? +

extract_fillable_fields. 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_fillable_fields? +

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

What risk level is extract_fillable_fields? +

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

Can I rate-limit extract_fillable_fields? +

Yes. Add a rate_limit block to the extract_fillable_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.

How do I block extract_fillable_fields completely? +

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

What MCP server provides extract_fillable_fields? +

extract_fillable_fields 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.