Medium Risk

fill_by_path

⭐ RECOMMENDED for template work! Fill multiple cells using path-based addressing. jkf87-style path format: "label > direction > direction" - "이름: > right" → find "이름:" and fill the cell to its right - "합계 > down > down" → find "합계" and fill 2 cells below - Directions: right, left, up, down Exam...

Part of the Hwpx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use fill_by_path to create or modify resources in Hwpx. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call fill_by_path repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Hwpx.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

hwpx.yaml
tools:
  fill_by_path:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Hwpx policy for all 135 tools.

Tool Name fill_by_path
Category Write
MCP Server Hwpx MCP Server
Risk Level Medium

View all 135 tools →

Agents calling write-class tools like fill_by_path have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the fill_by_path tool do? +

⭐ RECOMMENDED for template work! Fill multiple cells using path-based addressing. jkf87-style path format: "label > direction > direction" - "이름: > right" → find "이름:" and fill the cell to its right - "합계 > down > down" → find "합계" and fill 2 cells below - Directions: right, left, up, down Example: fill_by_path({ mappings: { "이름: > right": "홍길동", "연락처: > right": "010-1234-5678", "합계 > down": "1,000,000" } }) Much easier than specifying table_index, row, col manually!. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fill_by_path? +

Add a rule in your Intercept YAML policy under the tools section for fill_by_path. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hwpx MCP server.

What risk level is fill_by_path? +

fill_by_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit fill_by_path? +

Yes. Add a rate_limit block to the fill_by_path 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.

How do I block fill_by_path completely? +

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

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.