postmark_send_batch
Send multiple emails in a single Postmark API call (up to 500 messages).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/postmark-send-batch.md
What postmark_send_batch does on UnClick
AI agents use postmark_send_batch to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Postmark server token |
messages | array | Yes | Array of email message objects (same fields as send_email) |
Parameters from the server's own tool schema.
Why postmark_send_batch is rated Medium
This tool sends (creates) email messages via the Postmark service. Sending emails is a reversible write operation—messages can be unsent or deleted in some systems, and the primary effect is data creation/transmission rather than destruction or code execution.
From the tool's definition Tool name 'postmark_send_batch' and description 'Send multiple emails in a single Postmark API call' clearly indicate the tool creates and sends email messages.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs postmark_send_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For postmark_send_batch, this is the rule to start with:
postmark_send_batch 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 UnClick, apply this rule, and every postmark_send_batch call is checked against it from then on.
Questions about postmark_send_batch
Send multiple emails in a single Postmark API call (up to 500 messages). It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
postmark_send_batch accepts 2 parameters: api_key, messages. Required: api_key, messages. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for postmark_send_batch: 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 UnClick. Nothing to install.
postmark_send_batch 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 postmark_send_batch 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 postmark_send_batch. 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.
postmark_send_batch is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue