⭐ Build an entire document body in a SINGLE call. Instead of calling insert_paragraph 30+ times, pass all elements (paragraphs and tables) at once. TWO MODES: (1) Free-form — inline styles per element (bold/font_size/align/margin_*/line_spacing). (2) Template-styled — pass `template_profile` + p...
High parameter count (28 properties)
Part of the Hwpx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke build_document to trigger processes or run actions in Hwpx. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
build_document can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
build_document:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Hwpx policy for all 135 tools.
Agents calling execute-class tools like build_document have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
build_document is one of the high-risk operations in Hwpx. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
⭐ Build an entire document body in a SINGLE call. Instead of calling insert_paragraph 30+ times, pass all elements (paragraphs and tables) at once. TWO MODES: (1) Free-form — inline styles per element (bold/font_size/align/margin_*/line_spacing). (2) Template-styled — pass `template_profile` + per-element `preset` to reuse paraPrIDRef/charPrIDRef already defined in the document's header.xml. This mode ignores inline style fields so the result matches the template exactly, with no post-processing required. Template mode (gongmun_v1 example): build_document({ doc_id, template_profile: "gongmun_v1", after_index: 7, elements: [ { type: "paragraph", text: "□ 추진 배경", preset: "heading" }, { type: "paragraph", text: " ㅇ 2025년 대비 교육 니즈 확대", preset: "point" }, { type: "paragraph", text: " - 바이브 코딩·노코드 수요 급증", preset: "detail" }, { type: "table", rows: 5, cols: 3, header_preset: "table_header", body_preset: "table_body", data: [ ["차수","교육 주제","시간·정원"], ["1차","AI 기초","3H·40명"], ... ] } ] }) Built-in profiles: - gongmun_v1 — DGIST 공문서_프레임.hwpx. Presets: title, date, summary, heading, point, detail, subdetail, footnote, table_title, table_unit, table_note (table cell presets: table_header, table_body) When `template_profile` is supplied the server fingerprints the document's header.xml style palette and validates preset-relevant entries. If the opened document does not actually carry the profile's style palette, the call fails fast with a descriptive error so no wrong-styled content lands in the file.. It is categorised as a Execute tool in the Hwpx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for build_document. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hwpx MCP server.
build_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_document rule in your Intercept 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 Intercept policy for build_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.
build_document is provided by the Hwpx MCP server (hwpx-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.