update_domain_catch_all
Configure catch-all email forwarding for a domain. Unmatched emails will be forwarded to the destination. Internal targets (mailboxes on the same domain) work on all plans. External targets require Pro or Agency plan.
This record as markdown: /tools/trekmail-mcp-server/update-domain-catch-all.md
What update_domain_catch_all does on TrekMail MCP Server
AI agents use update_domain_catch_all to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
Why update_domain_catch_all is rated Medium
This tool modifies email infrastructure settings (catch-all forwarding rules) which can be changed or undone. It is a Write operation because it creates or modifies domain configuration reversibly. Severity is medium because misconfiguration could cause unintended email routing (business continuity impact) but doesn't delete data or move money.
From the tool's definition Tool description states 'Configure catch-all email forwarding for a domain' — the verb 'configure' and action of setting up forwarding rules indicates modification of domain email settings. This is reversible configuration change, not a destructive action.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs update_domain_catch_all 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 update_domain_catch_all, this is the rule to start with:
update_domain_catch_all 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 TrekMail MCP Server, apply this rule, and every update_domain_catch_all call is checked against it from then on.
Questions about update_domain_catch_all
Configure catch-all email forwarding for a domain. Unmatched emails will be forwarded to the destination. Internal targets (mailboxes on the same domain) work on all plans. External targets require Pro or Agency plan. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for update_domain_catch_all: 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.
update_domain_catch_all 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 update_domain_catch_all 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 update_domain_catch_all. 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.
update_domain_catch_all 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