This record as markdown: /tools/airmang-hwpx-mcp-server/create-document.md
What create_document does on Hwpx
AI agents use create_document to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.
Why create_document is rated Medium
Creating and immediately saving a new document is a reversible write operation. It creates new data artifacts (HWPX files) on the system. While reversible (the file can be deleted), this is a write action that commits new content to storage.
From the tool's definition Tool description states '새 HWPX 문서를 생성하고 즉시 저장합니다' (creates a new HWPX document and saves it immediately). The server description confirms it can 'modify HWPX documents directly'. The tool creates and saves new document files.
Attacks that exploit this kind of access
The rule that runs create_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_document, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every create_document call is checked against it from then on.
Questions about create_document
새 HWPX 문서를 생성하고 즉시 저장합니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwpx MCP server in PolicyLayer and add a rule for create_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 Hwpx. Nothing to install.
create_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 create_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 create_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.
create_document is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hwpx, and thousands of servers like it.
This server
Across the catalogue