Return absolute paths on the **user's local machine** (home, Documents, Downloads, skills/templates) plus a list of HWPX templates that are actually present on disk. Call this INSTEAD of running Bash `echo $HOME` / `cmd /c echo %USERPROFILE%` whenever a skill needs to locate user files. The MCP ...
Admin/system-level operation
Part of the Hwpx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_user_paths to retrieve information from Hwpx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_user_paths only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_user_paths:
rules:
- action: allowSee the full Hwpx policy for all 135 tools.
Agents calling read-class tools like get_user_paths have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Return absolute paths on the **user's local machine** (home, Documents, Downloads, skills/templates) plus a list of HWPX templates that are actually present on disk. Call this INSTEAD of running Bash `echo $HOME` / `cmd /c echo %USERPROFILE%` whenever a skill needs to locate user files. The MCP server runs under the user's own OS account, so the values it returns reflect the real filesystem — whereas a skill's Bash tool may execute inside a sandboxed container where `$HOME` is `/root` and the user's files are invisible. Typical usage from a skill: 1. Call `get_user_paths`. 2. Check `templates[]` for the filename you need (e.g. `공문서_프레임.hwpx`). 3. Pass `templates[i].path` to `open_document({ file_path: ... })`. 4. Build output filenames by joining `downloads` with your desired basename.. It is categorised as a Read tool in the Hwpx MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_user_paths. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hwpx MCP server.
get_user_paths is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user_paths rule in your Intercept 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 Intercept policy for get_user_paths. 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.
get_user_paths is provided by the Hwpx MCP server (hwpx-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.