List recent emails in an inbox. Returns sender, subject, and preview for each email.
AI agents call check_inbox 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.
This tool retrieves and queries email data without altering, deleting, or executing actions. It is a straightforward read operation that returns information about emails. The blast radius of misuse is minimal — an AI agent could read email contents but cannot send, delete, or modify messages. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool description states 'List recent emails in an inbox' and 'Returns sender, subject, and preview for each email' — purely retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
List recent emails in an inbox. Returns sender, subject, and preview for each email. 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 check_inbox: 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.
check_inbox 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 check_inbox 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 check_inbox. 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.
check_inbox 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 →