read_message

Get a single message by IMAP UID, including full body and attachment metadata. Requires a message token with messages:read scope.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/read-message.md

WHAT IT DOES

What read_message does on TrekMail MCP Server

AI agents call read_message 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.

RISK

Why read_message is rated Low

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

RECOMMENDED RULE

The rule that runs read_message 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 read_message, this is the rule to start with:

read_message Allowed

read_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_message": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every read_message call is checked against it from then on.

FAQ

Questions about read_message

What does the read_message tool do? +

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.

How do I enforce a policy on read_message? +

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.

What risk level is read_message? +

read_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_message? +

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.

How do I block read_message completely? +

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.

What MCP server provides read_message? +

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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →