Enhanced Markdown to HTML conversion with beautiful styling and theme support. Supports GitHub, Academic, Modern, and Default themes with complete style preservation. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-gener...
AI agents use convert_markdown_to_html 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.
This tool creates new files (HTML output) through a document conversion process. While file creation is reversible (files can be deleted), the tool modifies the filesystem by writing new artifacts.
From the tool's definition Tool converts markdown to HTML and automatically saves files to OUTPUT_DIR with auto-generated names. The description explicitly states 'Files will be automatically saved to OUTPUT_DIR' indicating file creation/writing capability.
Documented attack patterns abuse exactly the kind of access convert_markdown_to_html 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_html:
{
"version": "1",
"default": "deny",
"tools": {
"convert_markdown_to_html": {
"limits": [
{
"counter": "convert_markdown_to_html_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_markdown_to_html 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 HTML conversion with beautiful styling and theme support. Supports GitHub, Academic, Modern, and Default themes with complete style preservation. 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_html: 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_html 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_html 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_html. 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_html 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.