hwp_open

THE RISK

Low Risk

Why hwp_open needs a policy

Opening a document reads it from disk and loads it into the application. This is a read/access operation with no modification of data. The main risk is minimal — an agent could open arbitrary files — but no data is created, modified, or destroyed.

From the tool's definition Open an existing HWP document

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

POLICY

How to control hwp_open

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hwp_open": {}
  }
}

hwp_open is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register HWP MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More HWP MCP Server tools

Destructive hwp_close_all_documents 모든 문서를 닫습니다. Args: save: 저장 후 닫을지 여부 (기본값: False) suppress_dialog: 저장 Destructive hwp_close_window HWP 창을 닫습니다 (저장 안 함). Args: hwnd: 윈도우 핸들 (hwp_list_all_instances로 확인) Re Execute hwp_navigate hwp_navigate Execute hwp_batch_operations hwp_batch_operations Execute hwp_switch_tab 현재 HWP 창에서 특정 탭으로 전환합니다. Args: index: 탭 인덱스 (hwp_list_tabs로 확인) Returns: Execute hwp_switch_window 다른 HWP 창으로 전환합니다. Args: hwnd: 윈도우 핸들 (hwp_list_windows로 확인) Returns: Write hwp_close_document 현재 문서를 닫습니다. Args: save: 저장 후 닫을지 여부 (기본값: False) suppress_dialog: 저장 Write hwp_create Create a new HWP document.

All 30 HWP MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about hwp_open

What does the hwp_open tool do? +

Open an existing HWP document. It is categorised as a Read tool in the HWP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hwp_open? +

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

hwp_open is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hwp_open? +

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

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

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

CHECK YOUR STACK →