postmark_search_messages
Search sent messages in Postmark by recipient, sender, tag, or status.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/postmark-search-messages.md
What postmark_search_messages does on UnClick
AI agents call postmark_search_messages 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 |
|---|---|---|---|
tag | string | — | Filter by tag |
count | number | — | Number of messages to return (default 25) |
offset | number | — | Pagination offset |
status | string | — | Filter by status: queued, sent, bounced, etc. |
api_key | string | Yes | Postmark server token |
recipient | string | — | Filter by recipient email |
from_email | string | — | Filter by sender email |
Parameters from the server's own tool schema.
Why postmark_search_messages is rated Low
This tool retrieves and queries historical message data from Postmark without creating, modifying, deleting, or executing external operations. The search functionality is a standard Read operation typical of message audit or compliance features.
From the tool's definition Tool description explicitly states 'Search sent messages' with filtering by recipient, sender, tag, or status—all read-only query operations with no modification or deletion capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs postmark_search_messages 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_search_messages, this is the rule to start with:
postmark_search_messages 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_search_messages call is checked against it from then on.
Questions about postmark_search_messages
Search sent messages in Postmark by recipient, sender, tag, or status. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
postmark_search_messages accepts 7 parameters: tag, count, offset, status, api_key, recipient, from_email. 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_search_messages: 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_search_messages 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_search_messages 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_search_messages. 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_search_messages 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