search_and_replace

문서에서 텍스트를 치환합니다. 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/search-and-replace.md

WHAT IT DOES

What search_and_replace does on Hwpx

AI agents use search_and_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.

RISK

Why search_and_replace is rated Medium

This tool modifies document content by replacing text and persists changes unless dry_run=True is specified. It is a reversible write operation but with high blast radius since a broad search-and-replace across a document can cause widespread content changes that may be difficult to recover without versioning.

From the tool's definition '문서에서 텍스트를 치환합니다' (replaces text in document); 'dry_run=True이면 원본을 저장하지 않습니다' (if dry_run=True, original is not saved — implying default saves changes)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_and_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 search_and_replace, this is the rule to start with:

search_and_replace Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_and_replace": {
      "limits": [
        {
          "counter": "search_and_replace_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 search_and_replace call is checked against it from then on.

FAQ

Questions about search_and_replace

What does the search_and_replace 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 search_and_replace? +

Register the Hwpx MCP server in PolicyLayer and add a rule for search_and_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.

What risk level is search_and_replace? +

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

Can I rate-limit search_and_replace? +

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

How do I block search_and_replace completely? +

Set action: deny in the PolicyLayer policy for search_and_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.

What MCP server provides search_and_replace? +

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

KEEP EXPLORING

More on Hwpx, and thousands of servers like it.

This server

All 109 Hwpx tools →

Across the catalogue

generate_and_fetch_code on Stitch MCP Server → The MCP Attack Database →

Guides

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