List mailboxes on the TrekMail account. Supports filtering by domain and searching by address. Returns paginated results.
AI agents call list_mailboxes 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 queries and retrieves mailbox information with optional filtering and pagination. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is a straightforward data retrieval operation.
From the tool's definition Tool description states 'List mailboxes' and 'Returns paginated results' — classic read operation that retrieves data without modification. No destructive, write, execute, or financial keywords present.
Attacks that exploit this kind of access
List mailboxes on the TrekMail account. Supports filtering by domain and searching by address. Returns paginated results. 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 list_mailboxes: 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.
list_mailboxes 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_mailboxes 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_mailboxes. 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_mailboxes 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 →