AI agents use add_inbox_access 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.
This tool modifies access control by granting inbox access to teammates, which is a reversible change to system state. It does not delete data (Destructive), execute arbitrary code (Execute), handle financial transactions (Financial), or merely retrieve information (Read).
From the tool's definition Tool name 'add_inbox_access' and description 'Grant teammates access to an inbox' indicate creation or modification of access control settings. This is a write operation that changes permissions/access levels for a resource.
Documented attack patterns abuse exactly the kind of access add_inbox_access gives an agent:
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 add_inbox_access:
{
"version": "1",
"default": "deny",
"tools": {
"add_inbox_access": {
"limits": [
{
"counter": "add_inbox_access_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_inbox_access 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.
Free to start. No card required.
Grant teammates access to an 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.
Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_inbox_access is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
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.