mailpulse

SERVERPulsenetwork SOURCEhttps://pulse.theaslangroupllc.com/api/mcp

Critical RISK CLASS

Category Financial

Parameters 111 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/mailpulse.md

WHAT IT DOES

What mailpulse does on Pulsenetwork

AI agents use mailpulse to commit financial operations through Pulsenetwork, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`id`	string	—	Lob letter id returned by POST /api/letters
`to`	string	—	Recipient address
`from`	string	—	Sender-of-record address (never The Aslan Group LLC — we are a paid conduit only)
`lang`	string	—	Response language code (en \| es \| fr \| de \| zh \| hi \| ar \| pt \| ja \| ko \| etc.)
`action`	string	Yes	Which endpoint to call. Options: verify-address \| letters \| {id} \| health
`content`	string	—	{ html } or { file_url } — exactly one
`service`	string	—	standard \| certified \| certified_return_receipt \| international
`quote_id`	string	—	From POST /api/quote
`issued_at`	string	—	From POST /api/quote, copied verbatim
`amount_micro`	string	—	From POST /api/quote, copied verbatim
`client_request_id`	string	—	8-128 chars, unique per letter, enables idempotent retries

Parameters from the server's own tool schema.

RISK

Why mailpulse is rated Critical

Tool commits real financial payment and triggers irreversible physical mail delivery.

From the tool's definition paying causes real postage to print and mail, once payment settles

Risk signalsAccepts raw HTML/template content (content) · High parameter count (11 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mailpulse safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mailpulse, this is the rule to start with:

mailpulse Approval-gated

Any call to mailpulse is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mailpulse": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pulsenetwork, apply this rule, and every mailpulse call is checked against it from then on.

FAQ

Questions about mailpulse

What does the mailpulse tool do? +

MailPulse: The fleet's first ACTION origin — does something in the world instead of answering a question. Sends a real physical letter (US First-Class, US Certified with optional electronic return receipt, or international) via USPS through Lob's Print & Mail network: paying causes real postage to print and mail, once payment settles. Free address-deliverability check precedes the paid send; free price quote locks the exact price for 15 minutes; cheap status/tracking poll follows up afterward. Every response reports mode: "test" | "live" — test mode costs nothing and mails nothing physical. Coverage: US + international mail via USPS/Lob Endpoints: • verify-address ($0.01): Verify a mailing address (US + international) • letters ($3.00): THE paid action: prints and mails a real physical letter via Lob once payment settles. Price varies by service — standard $3.00, certified $12.00, certified_return_receipt $14.00, international $5.00 — the amount shown here is the representative/minimum price; the actual x402 charge always matches the caller's quote_id-verified order from POST /api/quote (free, no x402 gate). Requires a client_request_id (8-128 chars) for idempotency. • {id} ($0.005): Letter status / USPS tracking poll • health (FREE): Liveness + current mode. It is categorised as a Financial tool in the Pulsenetwork MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does mailpulse accept? +

mailpulse accepts 11 parameters: id, to, from, lang, action, content, service, quote_id, issued_at, amount_micro, client_request_id. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mailpulse? +

Register the Pulsenetwork MCP server in PolicyLayer and add a rule for mailpulse: 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 Pulsenetwork. Nothing to install.

What risk level is mailpulse? +

mailpulse is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mailpulse? +

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

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

mailpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pulsenetwork, and thousands of servers like it.

This server

All 80 Pulsenetwork tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →