get_forwarding_address_log
Recent deliveries for one forwarding address: when each message came in, who sent it, where it was forwarded, and the outcome — delivered, deferred, rejected by the recipient, or blocked as spam before forwarding. The window is the plan
This record as markdown: /tools/trekmail-mcp-server/get-forwarding-address-log.md
What get_forwarding_address_log does on TrekMail MCP Server
AI agents call get_forwarding_address_log 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_forwarding_address_log is rated Low
This tool is a pure data retrieval operation that returns metadata and status information about past email forwarding events. It has no side effects, cannot modify or delete data, and does not execute commands or trigger external operations. The information returned is read-only and historical in nature, making it a straightforward Read category tool with low severity and high confidence.
From the tool's definition The tool retrieves historical log data about forwarding deliveries ('Recent deliveries', 'when each message came in', 'who sent it', 'where it was forwarded', 'outcome').
Attacks that exploit this kind of access
The rule that runs get_forwarding_address_log 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_forwarding_address_log, this is the rule to start with:
get_forwarding_address_log 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_forwarding_address_log call is checked against it from then on.
Questions about get_forwarding_address_log
Recent deliveries for one forwarding address: when each message came in, who sent it, where it was forwarded, and the outcome — delivered, deferred, rejected by the recipient, or blocked as spam before forwarding. The window is the plan. 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_forwarding_address_log: 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_forwarding_address_log 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_forwarding_address_log 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_forwarding_address_log. 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_forwarding_address_log 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