Convert documents between formats with enhanced style preservation. Output directory is controlled by OUTPUT_DIR environment variable. All output files will be automatically saved to the directory specified by OUTPUT_DIR with auto-generated names. ⚠️ IMPORTANT: For Markdown to HTML conversion wit...
AI agents use convert_document 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 and writes new converted document files to the filesystem. While it doesn't delete or overwrite existing data irreversibly, it does create new files and the conversion process modifies document content. The automatic file generation and writing to OUTPUT_DIR constitutes a Write operation.
From the tool's definition Tool converts documents between formats and saves output files to a directory specified by OUTPUT_DIR with auto-generated names. The description indicates file creation/modification ('output files will be automatically saved').
Documented attack patterns abuse exactly the kind of access convert_document 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_document:
{
"version": "1",
"default": "deny",
"tools": {
"convert_document": {
"limits": [
{
"counter": "convert_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_document 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.
Convert documents between formats with enhanced style preservation. Output directory is controlled by OUTPUT_DIR environment variable. All output files will be automatically saved to the directory specified by OUTPUT_DIR with auto-generated names. ⚠️ IMPORTANT: For Markdown to HTML conversion with style preservation, use. 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_document: 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_document 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_document 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_document. 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_document 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.