Create a new email inbox. Returns an @lobstermail.ai address.
AI agents use create_inbox to create or update resources in Lobstermail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lobstermail environment.
Creating an inbox is a reversible write operation (the inbox can be deleted via delete_inbox). It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because email inboxes are communication channels; an attacker could create numerous inboxes for spam or impersonation, but the damage is containable and reversible.
From the tool's definition Tool description states 'Create a new email inbox' — this is a creation operation that modifies the account's data structure by adding a new inbox resource.
Attacks that exploit this kind of access
Create a new email inbox. Returns an @lobstermail.ai address. It is categorised as a Write tool in the Lobstermail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lobstermail MCP server in PolicyLayer and add a rule for create_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.
create_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →