byte_preserving_patch
section XML 바이트 splice 기반 문단 텍스트 패치를 적용합니다.
This record as markdown: /tools/airmang-hwpx-mcp-server/byte-preserving-patch.md
What byte_preserving_patch does on Hwpx
AI agents use byte_preserving_patch 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 byte_preserving_patch is rated Medium
This tool modifies document content (paragraphs within sections) reversibly through patching operations. While it operates at a low level (byte-level XML manipulation), the modifications are not described as destructive or irreversible. It fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name 'byte_preserving_patch' and description 'applies paragraph text patch based on section XML byte splice' indicate modification of document content. The description explicitly states patching/modifying paragraph text within XML sections.
Attacks that exploit this kind of access
The rule that runs byte_preserving_patch 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 byte_preserving_patch, this is the rule to start with:
byte_preserving_patch 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 byte_preserving_patch call is checked against it from then on.
Questions about byte_preserving_patch
section XML 바이트 splice 기반 문단 텍스트 패치를 적용합니다. 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 byte_preserving_patch: 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.
byte_preserving_patch 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 byte_preserving_patch 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 byte_preserving_patch. 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.
byte_preserving_patch 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