AI agents use hwp_save to create or update resources in HWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HWP MCP Server environment.
This tool modifies persistent state by writing document changes to storage, making it a Write operation. Severity is medium because misuse could overwrite important documents, but the action is reversible (previous versions may exist, or undo is possible).
From the tool's definition Tool name 'hwp_save' and description 'Save the current HWP document' indicate a write operation that persists document state to disk.
Documented attack patterns abuse exactly the kind of access hwp_save gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hwp_save:
{
"version": "1",
"default": "deny",
"tools": {
"hwp_save": {
"limits": [
{
"counter": "hwp_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}hwp_save 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.
Save the current HWP document. It is categorised as a Write tool in the HWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HWP MCP Server MCP server in PolicyLayer and add a rule for hwp_save: 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 MCP Server. Nothing to install.
hwp_save 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 hwp_save 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 hwp_save. 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.
hwp_save is provided by the HWP MCP Server MCP server (jkf87/hwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 HWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.