Get pre-populated forward data: subject (Fwd:), forwarded body, original attachment metadata.
AI agents call prepare_forward to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and pre-populates forward message data for composition purposes. It queries existing message content and metadata to prepare it for forwarding, but does not create, modify, delete, or execute any operations. The data is assembled for the user to review before action, making it a Read category tool with low severity since it only retrieves information without side effects.
From the tool's definition Tool description states it 'Get[s] pre-populated forward data' including subject, forwarded body, and attachment metadata. The verb 'get' and action of retrieving/preparing data for display indicates read-only behavior with no modifications.
Attacks that exploit this kind of access
Get pre-populated forward data: subject (Fwd:), forwarded body, original attachment metadata. 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 prepare_forward: 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.
prepare_forward 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 prepare_forward 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 prepare_forward. 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.
prepare_forward 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →