remove_memo
본문 문단 또는 표 셀 문단의 메모를 제거합니다. dry_run=True이면 원본을 저장하지 않습니다.
This record as markdown: /tools/airmang-hwpx-mcp-server/remove-memo.md
What remove_memo does on Hwpx
AI agents call remove_memo to permanently remove resources in Hwpx, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_memo is rated Critical
The tool removes memo annotations from document paragraphs or table cell paragraphs and by default persists the change to the original file. Without dry_run=True, the deletion is irreversible, placing this firmly in the Destructive category. The blast radius is high because misuse could permanently strip annotations from important documents.
From the tool's definition remove_memo — '메모를 제거합니다' (removes memo); dry_run=True이면 원본을 저장하지 않습니다 implies that by default (dry_run=False) the original document is overwritten/saved, making the removal irreversible.
Attacks that exploit this kind of access
The rule that runs remove_memo 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 remove_memo, this is the rule to start with:
remove_memo is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every remove_memo call is checked against it from then on.
Questions about remove_memo
본문 문단 또는 표 셀 문단의 메모를 제거합니다. dry_run=True이면 원본을 저장하지 않습니다. It is categorised as a Destructive tool in the Hwpx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hwpx MCP server in PolicyLayer and add a rule for remove_memo: 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.
remove_memo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_memo 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 remove_memo. 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.
remove_memo 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.
Across the catalogue