Search message summaries by sender, recipient, subject, or body.
AI agents call mailosaur_messages_search to retrieve information from Mailosaur MCP 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 message data based on search criteria without side effects. It does not create, modify, delete, execute code, or involve financial operations. It is a straightforward read operation on a testing service's message database.
From the tool's definition Tool name 'mailosaur_messages_search' and description 'Search message summaries by sender, recipient, subject, or body' indicate pure retrieval of existing data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search message summaries by sender, recipient, subject, or body. It is categorised as a Read tool in the Mailosaur MCP MCP Server, which means it retrieves data without modifying state.
Register the Mailosaur MCP server in PolicyLayer and add a rule for mailosaur_messages_search: 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 Mailosaur MCP. Nothing to install.
mailosaur_messages_search 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 mailosaur_messages_search 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 mailosaur_messages_search. 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.
mailosaur_messages_search is provided by the Mailosaur MCP server (mrnewdelhi/mailosaur-mcp). 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 →