Get a single message by IMAP UID, including full body and attachment metadata. Requires a message token with messages:read scope.
AI agents call read_message 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 message data by IMAP UID and returns the full body and attachment metadata. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. It is a straightforward read operation that queries existing email data. The scope requirement ('messages:read') further confirms read-only access.
From the tool's definition Tool name is 'read_message' and description states 'Get a single message' with 'messages:read scope' — purely retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get a single message by IMAP UID, including full body and attachment metadata. Requires a message token with messages:read scope. 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 read_message: 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.
read_message 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 read_message 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 read_message. 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.
read_message 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 →