mail_merge

A write tool on the Hwpx MCP server.

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/mail-merge.md

WHAT IT DOES

What mail_merge does on Hwpx

AI agents use mail_merge 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 mail_merge is rated Medium

Mail merge creates or modifies document content by substituting variables into document templates. This is a reversible write operation that modifies documents. While the description is empty, the context of a document editing server and the nature of mail merge functionality (generating variants of documents with inserted data) indicates this is a Write action.

From the tool's definition Tool name is 'mail_merge' and the server enables modification of HWPX documents. Mail merge typically generates and modifies multiple documents by inserting variable data into templates.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mail_merge Rate-limited

mail_merge 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": {
    "mail_merge": {
      "limits": [
        {
          "counter": "mail_merge_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 mail_merge call is checked against it from then on.

FAQ

Questions about mail_merge

What does the mail_merge tool do? +

mail_merge is a write tool on the Hwpx MCP server. 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 mail_merge? +

Register the Hwpx MCP server in PolicyLayer and add a rule for mail_merge: 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 mail_merge? +

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

Can I rate-limit mail_merge? +

Yes. Add a rate_limit block to the mail_merge 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 mail_merge completely? +

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

mail_merge 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

mail_create_draft on Apple Apps MCP → The MCP Attack Database →

Guides

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