list_mailbox_bounces
Same as list_domain_bounces but scoped to a single mailbox — useful for per-sender reputation triage. Returns per-recipient SMTP failures.
This record as markdown: /tools/trekmail-mcp-server/list-mailbox-bounces.md
What list_mailbox_bounces does on TrekMail MCP Server
AI agents call list_mailbox_bounces to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_mailbox_bounces is rated Low
This tool queries and retrieves bounce statistics for a specific mailbox—a diagnostic/monitoring function with no side effects. It scopes data to a single mailbox for reputation analysis but performs no write, delete, or execution operations. The blast radius of misuse is minimal; an attacker gains visibility into bounce patterns but cannot modify email infrastructure or trigger outbound operations.
From the tool's definition Tool name 'list_mailbox_bounces' and description 'Returns per-recipient SMTP failures' indicate data retrieval with no modification. The verb 'list' and the passive 'returns' confirm read-only operation.
Attacks that exploit this kind of access
The rule that runs list_mailbox_bounces safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_mailbox_bounces, this is the rule to start with:
list_mailbox_bounces 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 TrekMail MCP Server, apply this rule, and every list_mailbox_bounces call is checked against it from then on.
Questions about list_mailbox_bounces
Same as list_domain_bounces but scoped to a single mailbox — useful for per-sender reputation triage. Returns per-recipient SMTP failures. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for list_mailbox_bounces: 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 TrekMail MCP Server. Nothing to install.
list_mailbox_bounces 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 list_mailbox_bounces 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 list_mailbox_bounces. 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.
list_mailbox_bounces is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue