Replace an embedded image inside an .hwpx by overwriting its BinData/ ZIP entry with new file contents.
AI agents use replace_hwp_image to create or update resources in Hwp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwp environment.
This tool modifies an existing image within a document by overwriting its binary data. While destructive-sounding, the operation is reversible (the original image could be restored from backups or previous versions), making it Write rather than Destructive.
From the tool's definition Replace an embedded image inside an .hwpx by overwriting its BinData/ ZIP entry with new file contents. The words 'overwriting' and 'replace' indicate modification of existing data.
Documented attack patterns abuse exactly the kind of access replace_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 replace_hwp_image:
{
"version": "1",
"default": "deny",
"tools": {
"replace_hwp_image": {
"limits": [
{
"counter": "replace_hwp_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}replace_hwp_image 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.
Free to start. No card required.
Replace an embedded image inside an .hwpx by overwriting its BinData/ ZIP entry with new file contents. It is categorised as a Write tool in the Hwp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwp MCP server in PolicyLayer and add a rule for replace_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.
replace_hwp_image 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 replace_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.
Set action: deny in the PolicyLayer policy for replace_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.
replace_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.
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.