Low Risk

list_inboxes

List all inboxes accessible to the API token

How to control list_inboxes ↓

What list_inboxes does on Frontapp MCP Server

AI agents call list_inboxes to retrieve information from Frontapp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_inboxes needs a policy

This tool queries and returns a list of inboxes. It performs no creation, modification, deletion, code execution, or financial operations. The only risk is information disclosure (learning what inboxes exist), which is a low-severity read operation. The blast radius of misuse is limited to exposure of inbox metadata.

From the tool's definition Tool name is 'list_inboxes' and description states it 'List all inboxes accessible to the API token' — a pure retrieval operation with no modification or side effects.

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

How to control list_inboxes

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 list_inboxes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_inboxes": {}
  }
}

list_inboxes is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_inboxes

What does the list_inboxes tool do? +

List all inboxes accessible to the API token. It is categorised as a Read tool in the Frontapp MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_inboxes? +

Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for list_inboxes: 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 list_inboxes? +

list_inboxes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_inboxes? +

Yes. Add a rate_limit block to the list_inboxes 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 list_inboxes completely? +

Set action: deny in the PolicyLayer policy for list_inboxes. 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 list_inboxes? +

list_inboxes 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.