Medium Risk

create_inbox

Create a new inbox

How to control create_inbox ↓

What create_inbox does on Frontapp MCP Server

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

Medium Risk

Why create_inbox needs a policy

Creating an inbox is a Write operation—it creates a new resource that persists in the system. It is reversible (the inbox can be deleted), so it does not rise to Destructive.

From the tool's definition Tool name 'create_inbox' and description 'Create a new inbox' indicate irreversible creation of a new communication structure/resource within Frontapp. This is a state-changing operation that adds a persistent entity to the system.

Documented attack patterns abuse exactly the kind of access create_inbox gives an agent:

How to control create_inbox

PolicyLayer is an MCP gateway — it sits between your AI agents and Frontapp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_inbox:

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

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.

  1. Create a free account and register Frontapp MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_inbox

What does the create_inbox tool do? +

Create a new inbox. It is categorised as a Write tool in the Frontapp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_inbox? +

Register the Frontapp MCP Server 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 Frontapp MCP Server. 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 Frontapp MCP Server MCP server (zqushair/frontapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frontapp MCP Server tool call.

Start from Frontapp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

151 Frontapp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.