email_list_messages
List email messages in a mailbox, newest first. Returns envelope data (subject, from, to, date) without the full body.
This record as markdown: /tools/io-github-alifanov-scopegate/email-list-messages.md
What email_list_messages does on ScopeGate
AI agents call email_list_messages to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why email_list_messages is rated Low
This tool performs a retrieval operation on email metadata only, with no side effects. It does not modify, delete, execute, or commit financial actions. The restriction to envelope data (headers only, no body) further limits its impact. Classification as Read is appropriate; severity is low because exposure of email metadata, while sensitive, does not enable destructive or financial harm directly.
From the tool's definition Tool description states it 'List email messages in a mailbox' and 'Returns envelope data (subject, from, to, date) without the full body.' This is a pure read operation that retrieves message metadata without modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs email_list_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_list_messages, this is the rule to start with:
email_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 ScopeGate, apply this rule, and every email_list_messages call is checked against it from then on.
Questions about email_list_messages
List email messages in a mailbox, newest first. Returns envelope data (subject, from, to, date) without the full body. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for email_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 ScopeGate. Nothing to install.
email_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 email_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 email_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.
email_list_messages is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue