Critical Risk →

delete_hwp_image

Delete a BinData/ ZIP entry inside an .hwpx (effectively removes the embedded image bytes). Args: file_path, target (basename or full entry), output_path (optional).

How to control delete_hwp_image ↓

AI agents call delete_hwp_image to permanently remove resources in Hwp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes embedded image data from HWP/HWPX files. The description explicitly states it 'removes the embedded image bytes' and takes a target image to delete. This is a destructive operation that cannot be undone—once the image is removed from the document, it is lost.

From the tool's definition Delete a BinData/ ZIP entry inside an .hwpx (effectively removes the embedded image bytes)

Documented attack patterns abuse exactly the kind of access delete_hwp_image gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Hwp, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_hwp_image:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_hwp_image"
  ]
}

delete_hwp_image disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Hwp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_hwp_image tool do? +

Delete a BinData/ ZIP entry inside an .hwpx (effectively removes the embedded image bytes). Args: file_path, target (basename or full entry), output_path (optional). It is categorised as a Destructive tool in the Hwp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_hwp_image? +

Register the Hwp MCP server in PolicyLayer and add a rule for delete_hwp_image: 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 Hwp. Nothing to install.

What risk level is delete_hwp_image? +

delete_hwp_image is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_hwp_image? +

Yes. Add a rate_limit block to the delete_hwp_image 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.

How do I block delete_hwp_image completely? +

Set action: deny in the PolicyLayer policy for delete_hwp_image. 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.

What MCP server provides delete_hwp_image? +

delete_hwp_image is provided by the Hwp MCP server (treesoop/hwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hwp tool call.

Deterministic rules across all 31 Hwp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

31 Hwp tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.