Insert a new image into an .hwpx — adds the file to BinData/, registers it in content.hpf, and appends a paragraph with an inline <hp:pic>. Args: file_path, source_path, ext (png/jpg/bmp/gif; auto from source_path if omitted), output_path (optional).
AI agents use insert_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.
The tool creates new content (image insertion) and modifies document structure (registers in BinData, content.hpf, appends paragraphs) but does not delete data, execute arbitrary code, or trigger financial transactions. These modifications are reversible (images can be deleted, paragraphs removed).
From the tool's definition Tool description states it 'Insert[s] a new image into an .hwpx' and 'adds the file to BinData/, registers it in content.hpf, and appends a paragraph' — these are reversible create/modify operations typical of Write category.
Documented attack patterns abuse exactly the kind of access insert_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 insert_hwp_image:
{
"version": "1",
"default": "deny",
"tools": {
"insert_hwp_image": {
"limits": [
{
"counter": "insert_hwp_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} insert_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.
Insert a new image into an .hwpx — adds the file to BinData/, registers it in content.hpf, and appends a paragraph with an inline <hp:pic>. Args: file_path, source_path, ext (png/jpg/bmp/gif; auto from source_path if omitted), output_path (optional). 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 insert_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.
insert_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 insert_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 insert_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.
insert_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.