remove_inbox_access

THE RISK

Critical Risk

Why remove_inbox_access needs a policy

Removing inbox access revokes permissions for teammates, which is a destructive administrative action. While access can technically be re-granted, this is an access control change that can immediately disrupt workflows and communication flows for affected users. The blast radius is high as it could prevent teammates from accessing customer communications they need to do their jobs.

From the tool's definition 'Remove teammates access from an inbox' — revokes access permissions, which is an irreversible or hard-to-recover action affecting user access control

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

POLICY

How to control remove_inbox_access

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_inbox_access"
  ]
}

remove_inbox_access disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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 →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Frontapp MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_inbox_access

What does the remove_inbox_access tool do? +

Remove teammates access from an inbox. It is categorised as a Destructive tool in the Frontapp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_inbox_access? +

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

remove_inbox_access is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_inbox_access? +

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

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

remove_inbox_access 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 →