This record as markdown: /tools/io-github-heznpc-iconnect/list-messages.md
What list_messages does on Iconnect
AI agents call list_messages 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.
Why list_messages is rated Low
This tool retrieves/queries message data from a mailbox without side effects. It does not create, modify, delete, or execute external operations. The verb 'list' and the context of reading messages from a mailbox clearly place this in the Read category. The severity is low because accessing message metadata or content does not cause irreversible changes, though exposure to sensitive email content is a consideration.
From the tool's definition Tool name 'list_messages' and description 'List recent messages in a mailbox' indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs list_messages 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 list_messages, this is the rule to start with:
list_messages 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 Iconnect, apply this rule, and every list_messages call is checked against it from then on.
Questions about list_messages
List recent messages in a mailbox (e.g. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for list_messages: 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.
list_messages 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 list_messages 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 list_messages. 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.
list_messages 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.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue