This record as markdown: /tools/airmang-hwpx-mcp-server/copy-document.md
What copy_document does on Hwpx
AI agents use copy_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 copy_document is rated Medium
Copying a document creates a new file but does not modify or delete existing data. The operation is fully reversible—the copied file can be deleted if needed. This falls squarely in the Write category (creates data reversibly) rather than Destructive.
From the tool's definition Tool name 'copy_document' with description stating it copies an HWPX document to a new path while preserving the original. This is a reversible data creation operation (copying an existing file to a new location).
Attacks that exploit this kind of access
The rule that runs copy_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 copy_document, this is the rule to start with:
copy_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 copy_document call is checked against it from then on.
Questions about copy_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 copy_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.
copy_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 copy_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 copy_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.
copy_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