# create_inbox

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

Agent View of the PolicyLayer registry record for `create_inbox`. HTML page: https://policylayer.com/tools/dev-agenticemail-mcp/create-inbox

## Facts

- Tool: `create_inbox`
- Server: AgenticEmail (`https://api.agenticemail.dev/mcp`) — https://policylayer.com/tools/dev-agenticemail-mcp.md
- Homepage: https://github.com/https://api.agenticemail.dev/mcp
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server auth posture: gated
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `domain` | string | no |  |
| `username` | string | no |  |
| `display_name` | string | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_inbox",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches AgenticEmail:

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

## Other tools on AgenticEmail (8)

- `get_message` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/get-message.md
- `get_thread` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/get-thread.md
- `list_inboxes` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-inboxes.md
- `list_messages` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-messages.md
- `list_threads` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-threads.md
- `read_attachment` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/read-attachment.md
- `reply_to_message` — Write — https://policylayer.com/tools/dev-agenticemail-mcp/reply-to-message.md
- `send_message` — Write — https://policylayer.com/tools/dev-agenticemail-mcp/send-message.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-agenticemail-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agenticemail-mcp