High-risk tools in Doc2x MCP Server
6 of the 14 tools in Doc2x MCP Server are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
doc2x_convert_export_waitExecuteWait for an export job to finish. Prefer calling doc2x_convert_export_submit first, then wait with uid+to. For backward compatibility, if formula_mode is provided and this job w...
-
doc2x_parse_image_layout_submitExecuteCreate an async image-layout parse task and return {uid}. After this, call doc2x_parse_image_layout_wait_text (with uid) or doc2x_parse_image_layout_status.
-
doc2x_parse_image_layout_syncExecuteParse an image layout synchronously and return the raw Doc2x result JSON (including convert_zip when present).
-
doc2x_parse_image_layout_wait_textExecuteWait for an image-layout parse task until success, returning first page markdown. Prefer passing uid (no re-submit). If only image_path is provided, it will (a) reuse an in-proc...
-
doc2x_parse_pdf_submitExecuteCreate a Doc2x PDF parse task for a local file and return {uid}. Prefer calling doc2x_parse_pdf_status to monitor progress/result; only call doc2x_parse_pdf_wait_text if the use...
-
doc2x_parse_pdf_wait_textExecuteWait for a PDF parse task until success and return merged text. Prefer passing uid (no re-submit). If only pdf_path is provided, it will (a) reuse an in-process cached uid if av...
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.