Wait for an incoming email matching optional filters.
AI agents call wait_for_email to retrieve information from Lobstermail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool waits and retrieves an email matching filters, which is a read/query operation with no side effects. It does not send, modify, or delete anything. Severity is low as it only reads incoming email data, though there is slight uncertainty about whether 'waiting' could trigger any side effects not described.
From the tool's definition 'Wait for an incoming email matching optional filters' — this tool retrieves/monitors for incoming email data without modifying anything
Attacks that exploit this kind of access
Wait for an incoming email matching optional filters. It is categorised as a Read tool in the Lobstermail MCP Server, which means it retrieves data without modifying state.
Register the Lobstermail MCP server in PolicyLayer and add a rule for wait_for_email: 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 Lobstermail. Nothing to install.
wait_for_email 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 wait_for_email 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 wait_for_email. 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.
wait_for_email is provided by the Lobstermail MCP server (lobster-kit/mcp-server-lobstermail). 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 →