extract_images

A read tool on the Docx MCP server.

SERVERDocx SOURCEandrew82106/llm_docx_agent_mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/andrew82106-llm-docx-agent-mcp/extract-images.md

WHAT IT DOES

What extract_images does on Docx

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

Extracting images from documents is a data retrieval operation with no side effects or modifications. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could exfiltrate images but cannot damage documents or systems. Low confidence reflects the empty tool description, but the name and server context strongly indicate a read-only operation.

From the tool's definition Tool name 'extract_images' indicates retrieval of image data from documents. Server description confirms 'image extraction' as a capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

extract_images Allowed

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

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

FAQ

Questions about extract_images

What does the extract_images tool do? +

extract_images is a read tool on the Docx MCP server. 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 extract_images? +

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

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

Can I rate-limit extract_images? +

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

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

extract_images is provided by the Docx MCP server (andrew82106/llm_docx_agent_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 24 Docx tools →

Across the catalogue

browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

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