AI agents call export_markdown to retrieve information from Docx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'export_markdown' implies reading a Word document and converting/exporting its content to Markdown format, which is a read/query operation with no side effects on the source document. However, since the description is empty, confidence is reduced — it could potentially write a file to disk.
From the tool's definition Tool name 'export_markdown' suggests reading/converting document content to markdown format; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access export_markdown gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for export_markdown:
{
"version": "1",
"default": "deny",
"tools": {
"export_markdown": {}
}
}export_markdown is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_markdown. 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 export_markdown: 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.
export_markdown 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 export_markdown 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 export_markdown. 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.
export_markdown 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.
Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.