Convert a DOCX file to HTML with embedded images as base64 data URIs
AI agents call convert_docx_to_html_with_images to retrieve information from Mammoth MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads an existing DOCX file and converts its content to HTML with base64-encoded images. It is a read/transform operation with no side effects on external systems; it does not write, delete, execute code, or involve financial transactions. The only potential concern is reading local files, which is inherently low risk.
From the tool's definition 'Convert a DOCX file to HTML with embedded images as base64 data URIs' — reads and transforms a file, embedding images as base64 data URIs in the output
Attacks that exploit this kind of access
Convert a DOCX file to HTML with embedded images as base64 data URIs. It is categorised as a Read tool in the Mammoth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mammoth MCP Server MCP server in PolicyLayer and add a rule for convert_docx_to_html_with_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 Mammoth MCP Server. Nothing to install.
convert_docx_to_html_with_images 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 convert_docx_to_html_with_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.
Set action: deny in the PolicyLayer policy for convert_docx_to_html_with_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.
convert_docx_to_html_with_images is provided by the Mammoth MCP Server MCP server (orchardxyz/mammoth-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →