get_inbox

THE RISK

Low Risk

Why get_inbox needs a policy

This tool retrieves inbox details by ID, which is a read-only query operation. No data is created, modified, deleted, or executed. The tool has minimal blast radius as it only exposes existing inbox metadata that the authenticated user should have access to.

From the tool's definition Tool name is 'get_inbox' and description states 'Get details of a specific inbox by ID' - purely retrieves information without modification or side effects.

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

POLICY

How to control get_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 get_inbox:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_inbox": {}
  }
}

get_inbox is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Frontapp MCP Server tools

Destructive delete_account Delete an account Destructive delete_contact Delete a contact Destructive delete_contact_group Delete a contact group Destructive delete_contact_handle Delete a handle from a contact Destructive delete_contact_list Delete a contact list Destructive delete_conversation_followers Remove followers from a conversation Destructive delete_draft Delete a draft Destructive delete_message_template Delete a message template

All 151 Frontapp MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_inbox

What does the get_inbox tool do? +

Get details of a specific inbox by ID. 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 get_inbox? +

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

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

Can I rate-limit get_inbox? +

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

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

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

CHECK YOUR STACK →