create_inbox

Create a new inbox. Omit username for a random one; omit domain to use the default (or only verified) domain.

SERVERAgenticEmail SOURCEhttps://api.agenticemail.dev/mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/dev-agenticemail-mcp/create-inbox.md

WHAT IT DOES

What create_inbox does on AgenticEmail

AI agents use create_inbox to create or update resources in AgenticEmail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AgenticEmail environment.

Parameter	Type	Required
`domain`	string	—
`username`	string	—
`display_name`	string	—

Parameters from the server's own tool schema.

RISK

Why create_inbox is rated Medium

This tool creates or modifies data (a new inbox resource) without permanently deleting or overwriting existing data, making it a Write operation. The severity is medium because creating inboxes could be abused to spam, create throwaway accounts for phishing, or evade monitoring, but the action is reversible (inboxes can be deleted).

From the tool's definition Tool name and description indicate it 'Create a new inbox' which is a reversible data creation operation. The tool creates a new resource (an inbox) in the email system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_inbox safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AgenticEmail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_inbox, this is the rule to start with:

create_inbox Rate-limited

create_inbox stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_inbox": {
      "limits": [
        {
          "counter": "create_inbox_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AgenticEmail, apply this rule, and every create_inbox call is checked against it from then on.

FAQ

Questions about create_inbox

What does the create_inbox tool do? +

Create a new inbox. Omit username for a random one; omit domain to use the default (or only verified) domain. It is categorised as a Write tool in the AgenticEmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_inbox accept? +

create_inbox accepts 3 parameters: domain, username, display_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_inbox? +

Register the AgenticEmail 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 AgenticEmail. Nothing to install.

What risk level is create_inbox? +

create_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_inbox? +

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.

How do I block create_inbox completely? +

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.

What MCP server provides create_inbox? +

create_inbox is provided by the AgenticEmail MCP server (https://api.agenticemail.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AgenticEmail, and thousands of servers like it.

This server

All 9 AgenticEmail tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →