batch_replace
여러 치환 규칙을 순서대로 적용합니다. dry_run=True이면 원본을 저장하지 않습니다.
This record as markdown: /tools/airmang-hwpx-mcp-server/batch-replace.md
What batch_replace does on Hwpx
AI agents use batch_replace 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.
Why batch_replace is rated Medium
batch_replace modifies document content by applying substitution rules. While the dry_run parameter allows preview without persistence, the primary function is to create or modify data within HWPX documents. This is a Write operation rather than Execute because it performs structured document modifications (text replacement) rather than arbitrary code execution.
From the tool's definition Tool description indicates 'batch_replace' applies multiple substitution rules in sequence. The note 'dry_run=True이면 원본을 저장하지 않습니다' (if dry_run=True, does not save the original) implies that when dry_run=False (the default behavior), the tool modifies and…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_replace 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 batch_replace, this is the rule to start with:
batch_replace 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every batch_replace call is checked against it from then on.
Questions about batch_replace
여러 치환 규칙을 순서대로 적용합니다. 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.
Register the Hwpx MCP server in PolicyLayer and add a rule for batch_replace: 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.
batch_replace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the batch_replace 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 batch_replace. 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.
batch_replace 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.
More on Hwpx, and thousands of servers like it.
This server
Across the catalogue