read_message

Read full content of an email message by ID. Content length is configurable (default: 5000 chars, max: 100000).

SERVERIconnect SOURCEiconnect-mcp

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/io-github-heznpc-iconnect/read-message.md

WHAT IT DOES

What read_message does on Iconnect

AI agents call read_message to retrieve information from Iconnect 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

The tool queries and retrieves email content by identifier. It performs a pure read operation on existing data with configurable limits. There is no creation, modification, deletion, execution, or financial impact. The only minor concern is information disclosure if an agent accesses unauthorized emails, but the tool itself is fundamentally a Read operation with low severity in isolation.

From the tool's definition Tool name is 'read_message' and description states 'Read full content of an email message by ID' — this is a retrieval operation with no modification or side effects.

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 Iconnect, 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 Iconnect, 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? +

Read full content of an email message by ID. Content length is configurable (default: 5000 chars, max: 100000). It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_message? +

Register the Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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