AI agents use create_teammate_group 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 creates a new contact group, which is reversible—the group can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money. It falls squarely into the Write category.
From the tool's definition Tool name 'create_teammate_group' and description 'Create a contact group for a teammate' indicate data creation. The verb 'Create' and context of group formation shows this is a Write operation that creates new organizational data.
Documented attack patterns abuse exactly the kind of access create_teammate_group 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 create_teammate_group:
{
"version": "1",
"default": "deny",
"tools": {
"create_teammate_group": {
"limits": [
{
"counter": "create_teammate_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_teammate_group 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.
Create a contact group for a teammate. 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 create_teammate_group: 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.
create_teammate_group 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 create_teammate_group 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 create_teammate_group. 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.
create_teammate_group 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.