Enhanced Markdown to DOCX conversion with professional styling and theme support. Preserves formatting, supports tables, lists, headings, and inline formatting with beautiful Word document output. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved...
AI agents use convert_markdown_to_docx to create or update resources in Doc Ops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc Ops environment.
The tool generates and writes new Word documents to disk based on Markdown input. This is a Write operation because it creates new files (reversible modification). While it processes documents, it does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool creates new DOCX files from Markdown input ('Markdown to DOCX conversion', 'Files will be automatically saved to OUTPUT_DIR'). This is document creation/generation with reversible file operations.
Documented attack patterns abuse exactly the kind of access convert_markdown_to_docx gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_markdown_to_docx:
{
"version": "1",
"default": "deny",
"tools": {
"convert_markdown_to_docx": {
"limits": [
{
"counter": "convert_markdown_to_docx_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_markdown_to_docx stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enhanced Markdown to DOCX conversion with professional styling and theme support. Preserves formatting, supports tables, lists, headings, and inline formatting with beautiful Word document output. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. It is categorised as a Write tool in the Doc Ops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc Ops MCP server in PolicyLayer and add a rule for convert_markdown_to_docx: 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 Doc Ops. Nothing to install.
convert_markdown_to_docx is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_markdown_to_docx 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_markdown_to_docx. 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_markdown_to_docx is provided by the Doc Ops MCP server (tele-ai/doc-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Doc Ops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Doc Ops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.