Hwpx

135 tools. 69 can modify or destroy data without limits.

10 destructive tools with no built-in limits. Policy required.

Last updated:

69 can modify or destroy data
66 read-only
135 tools total
Read (66) Write / Execute (59) Destructive / Financial (10)

Destructive tools (delete_image, delete_memo, delete_paragraph) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (apply_style, batch_fill_table, batch_replace) modify state. Without rate limits, an agent can make hundreds of changes in seconds β€” faster than any human can review or revert.

Execute tools (build_document, build_position_index) trigger processes with side effects. Builds, notifications, workflows β€” all fired without throttling.

Deny destructive operations
delete_image:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
apply_style:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
analyze_xml:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent delete data through the Hwpx MCP server? +

Yes. The Hwpx server exposes 10 destructive tools including delete_image, delete_memo, delete_paragraph. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Hwpx? +

The Hwpx server has 57 write tools including apply_style, batch_fill_table, batch_replace. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Hwpx MCP server expose? +

135 tools across 4 categories: Destructive, Execute, Read, Write. 66 are read-only. 69 can modify, create, or delete data.

How do I add Intercept to my Hwpx setup? +

One line change. Instead of running the Hwpx server directly, prefix it with Intercept: intercept -c hwpx.yaml -- npx -y @hwpx-mcp-server. Download a pre-built policy from policylayer.com/policies/hwpx and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

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.