AI agents use invite_team_member to create or update resources in Codemagic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codemagic MCP Server environment.
The tool creates a new team member record/invitation, which is a reversible write operation. It does not delete data (thus not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read data (not Read).
From the tool's definition Tool name is 'invite_team_member' and description states 'Invite a new team member to your team.' This creates a new team membership relationship.
Documented attack patterns abuse exactly the kind of access invite_team_member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codemagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for invite_team_member:
{
"version": "1",
"default": "deny",
"tools": {
"invite_team_member": {
"limits": [
{
"counter": "invite_team_member_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}invite_team_member 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.
Invite a new team member to your team. It is categorised as a Write tool in the Codemagic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codemagic MCP Server MCP server in PolicyLayer and add a rule for invite_team_member: 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 Codemagic MCP Server. Nothing to install.
invite_team_member 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 invite_team_member 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 invite_team_member. 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.
invite_team_member is provided by the Codemagic MCP Server MCP server (stefanoamorelli/codemagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codemagic 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.
16 Codemagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.