postmark_get_delivery_stats
Get delivery statistics from Postmark including bounces, spam complaints, and open rates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/postmark-get-delivery-stats.md
What postmark_get_delivery_stats does on UnClick
AI agents call postmark_get_delivery_stats to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Postmark server token |
Parameters from the server's own tool schema.
Why postmark_get_delivery_stats is rated Low
This tool retrieves historical email delivery analytics and metrics from Postmark. It performs a query operation with no side effects: it does not create, modify, delete, or reverse any data, nor does it execute code or commit financial obligations. The returned statistics are informational only, posing minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name includes 'get' and description states 'Get delivery statistics' with read-only metrics (bounces, spam complaints, open rates) — no data modification, deletion, or financial action indicated.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs postmark_get_delivery_stats 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_get_delivery_stats, this is the rule to start with:
postmark_get_delivery_stats is read-only, so it stays allowed. 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_get_delivery_stats call is checked against it from then on.
Questions about postmark_get_delivery_stats
Get delivery statistics from Postmark including bounces, spam complaints, and open rates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
postmark_get_delivery_stats accepts 1 parameter: api_key. Required: api_key. 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_get_delivery_stats: 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_get_delivery_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the postmark_get_delivery_stats 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_get_delivery_stats. 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_get_delivery_stats 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