Remove a contact from an account
AI agents use remove_contact_from_account 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.
Removing a contact from an account is a reversible association change — the contact still exists and can be re-added. This is a Write-level modification rather than Destructive because no data is permanently deleted; it only changes a relationship between entities.
From the tool's definition Remove a contact from an account
Documented attack patterns abuse exactly the kind of access remove_contact_from_account 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 remove_contact_from_account:
{
"version": "1",
"default": "deny",
"tools": {
"remove_contact_from_account": {
"limits": [
{
"counter": "remove_contact_from_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} remove_contact_from_account 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.
Remove a contact from an account. 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 remove_contact_from_account: 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.
remove_contact_from_account 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 remove_contact_from_account 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 remove_contact_from_account. 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.
remove_contact_from_account 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.