AI agents use add_team_member to create or update resources in Forgejo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
This tool creates or modifies data (team membership) reversibly. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because adding unauthorized members to a team could escalate access to repositories and resources managed by that team, potentially compromising confidentiality or enabling further malicious actions, but the action itself is reversible.
From the tool's definition 'Add a member to a team' modifies team membership by creating a new association between a user and a team, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access add_team_member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for add_team_member:
{
"version": "1",
"default": "deny",
"tools": {
"add_team_member": {
"limits": [
{
"counter": "add_team_member_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Add a member to a team. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for add_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 Forgejo. Nothing to install.
add_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 add_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 add_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.
add_team_member is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Forgejo, 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.
103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.