get_domain_deliverability
Get the outbound deliverability rollup for a domain — sent, delivered, soft/hard bounce counts, delivery rate, bounce rate, and health status (good/warning/poor). Mirrors the stats cards on the domain detail page.
This record as markdown: /tools/trekmail-mcp-server/get-domain-deliverability.md
What get_domain_deliverability does on TrekMail MCP Server
AI agents call get_domain_deliverability 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 get_domain_deliverability is rated Low
This tool performs a read-only query of email domain statistics and metrics. It returns aggregated data about email delivery performance without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an agent could only retrieve information about a domain's email statistics, which does not compromise data integrity or trigger external actions.
From the tool's definition Tool retrieves and queries deliverability metrics (sent, delivered, bounce counts, delivery rate, bounce rate, health status) with no modification capability — 'Get the outbound deliverability rollup' and 'Mirrors the stats cards' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_domain_deliverability 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 get_domain_deliverability, this is the rule to start with:
get_domain_deliverability 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 get_domain_deliverability call is checked against it from then on.
Questions about get_domain_deliverability
Get the outbound deliverability rollup for a domain — sent, delivered, soft/hard bounce counts, delivery rate, bounce rate, and health status (good/warning/poor). Mirrors the stats cards on the domain detail page. 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 get_domain_deliverability: 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.
get_domain_deliverability 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 get_domain_deliverability 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 get_domain_deliverability. 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.
get_domain_deliverability 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