다른 HWP 창으로 전환합니다. Args: hwnd: 윈도우 핸들 (hwp_list_windows로 확인) Returns: str: 결과 메시지
AI agents invoke hwp_switch_window to trigger actions in HWP MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool switches focus/control to a different HWP window using a window handle. It triggers an external UI/application operation rather than simply reading data or writing document content. The blast radius is low since it only changes which window is active, with no data modification or deletion.
From the tool's definition "다른 HWP 창으로 전환합니다" (Switch to another HWP window) — triggers an external operation on the HWP application window using a window handle
Documented attack patterns abuse exactly the kind of access hwp_switch_window 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_switch_window:
{
"version": "1",
"default": "deny",
"tools": {
"hwp_switch_window": {
"limits": [
{
"counter": "hwp_switch_window_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}hwp_switch_window stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
다른 HWP 창으로 전환합니다. Args: hwnd: 윈도우 핸들 (hwp_list_windows로 확인) Returns: str: 결과 메시지. It is categorised as a Execute tool in the HWP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HWP MCP Server MCP server in PolicyLayer and add a rule for hwp_switch_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.
hwp_switch_window is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hwp_switch_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.
Set action: deny in the PolicyLayer policy for hwp_switch_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.
hwp_switch_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.
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.