fill_by_path

라벨 경로 문법으로 셀을 채웁니다. dry_run=True이면 원본을 저장하지 않습니다.

SERVERHwpx SOURCEairmang/hwpx-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/airmang-hwpx-mcp-server/fill-by-path.md

WHAT IT DOES

What fill_by_path does on Hwpx

AI agents use fill_by_path to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.

RISK

Why fill_by_path is rated Medium

The tool creates or modifies cell content within HWPX documents. While it supports a dry-run mode for non-destructive preview, the primary function is to write/fill data into cells. This is reversible modification (cells can be re-filled or cleared), so it maps to Write rather than Destructive.

From the tool's definition Tool name 'fill_by_path' and description indicate it fills cells using label path syntax. The mention of 'dry_run=True' parameter implies the tool modifies document content (cells) and has a mode to preview changes without persisting them, confirming write…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fill_by_path safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fill_by_path, this is the rule to start with:

fill_by_path Rate-limited

fill_by_path stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fill_by_path": {
      "limits": [
        {
          "counter": "fill_by_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every fill_by_path call is checked against it from then on.

FAQ

Questions about fill_by_path

What does the fill_by_path tool do? +

라벨 경로 문법으로 셀을 채웁니다. dry_run=True이면 원본을 저장하지 않습니다. 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? +

Register the Hwpx MCP server in PolicyLayer and add a rule for fill_by_path: 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 Hwpx. Nothing to install.

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 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 fill_by_path completely? +

Set action: deny in the PolicyLayer 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 (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hwpx, and thousands of servers like it.

This server

All 109 Hwpx tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →