Critical Risk →

hwp_close_all_documents

모든 문서를 닫습니다. Args: save: 저장 후 닫을지 여부 (기본값: False) suppress_dialog: 저장 확인 팝업창 표시 안함 (기본값: True) Returns: str: 결과 메시지

How to control hwp_close_all_documents ↓

What hwp_close_all_documents does on HWP MCP Server

AI agents call hwp_close_all_documents 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_all_documents needs a policy

This tool closes ALL open documents with save defaulting to False and dialog suppression defaulting to True — meaning unsaved changes across all open documents would be silently discarded. This is irreversible data loss at scale (all documents), making it Destructive with high severity.

From the tool's definition 모든 문서를 닫습니다 (closes all documents); save parameter defaults to False, suppress_dialog defaults to True

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

How to control hwp_close_all_documents

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

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

hwp_close_all_documents 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_all_documents

What does the hwp_close_all_documents tool do? +

모든 문서를 닫습니다. Args: save: 저장 후 닫을지 여부 (기본값: False) suppress_dialog: 저장 확인 팝업창 표시 안함 (기본값: True) 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_all_documents? +

Register the HWP MCP Server MCP server in PolicyLayer and add a rule for hwp_close_all_documents: 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_all_documents? +

hwp_close_all_documents 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_all_documents? +

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

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

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