Critical Risk →

hwp_close_window

HWP 창을 닫습니다 (저장 안 함). Args: hwnd: 윈도우 핸들 (hwp_list_all_instances로 확인) Returns: str: 결과 메시지

How to control hwp_close_window ↓

What hwp_close_window does on HWP MCP Server

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

Critical Risk

Why hwp_close_window needs a policy

The tool explicitly closes a document window without saving, meaning any unsaved changes are permanently lost. This is an irreversible action — once closed without saving, the unsaved work cannot be recovered. This qualifies as Destructive due to the irreversible loss of data.

From the tool's definition HWP 창을 닫습니다 (저장 안 함) — 'closes the HWP window without saving'

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

How to control hwp_close_window

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_close_window:

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

hwp_close_window 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 MCP Server — 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.

Related tools and policies

Go deeper

Questions about hwp_close_window

What does the hwp_close_window tool do? +

HWP 창을 닫습니다 (저장 안 함). Args: hwnd: 윈도우 핸들 (hwp_list_all_instances로 확인) Returns: str: 결과 메시지. It is categorised as a Destructive tool in the HWP MCP Server 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 hwp_close_window? +

Register the HWP MCP Server MCP server in PolicyLayer and add a rule for hwp_close_window: 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.

What risk level is hwp_close_window? +

hwp_close_window 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 hwp_close_window? +

Yes. Add a rate_limit block to the hwp_close_window 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 hwp_close_window completely? +

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

hwp_close_window 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.

Enforce policy on every HWP MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.