remove_team_repo

Remove a repository from a team

SERVERForgejo SOURCEsqcows/forgejo-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/remove-team-repo.md

WHAT IT DOES

What remove_team_repo does on Forgejo

AI agents call remove_team_repo to permanently remove resources in Forgejo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_team_repo is rated Critical

Removing a repository from a team revokes access irreversibly without deleting, but is a significant destructive action.

From the tool's definition Remove a repository from a team

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_team_repo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_team_repo, this is the rule to start with:

remove_team_repo Hidden

remove_team_repo is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_team_repo"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every remove_team_repo call is checked against it from then on.

FAQ

Questions about remove_team_repo

What does the remove_team_repo tool do? +

Remove a repository from a team. It is categorised as a Destructive tool in the Forgejo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_team_repo? +

Register the Forgejo MCP server in PolicyLayer and add a rule for remove_team_repo: 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.

What risk level is remove_team_repo? +

remove_team_repo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_team_repo? +

Yes. Add a rate_limit block to the remove_team_repo 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.

How do I block remove_team_repo completely? +

Set action: deny in the PolicyLayer policy for remove_team_repo. 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.

What MCP server provides remove_team_repo? +

remove_team_repo 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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →remove_video on Mcptube Vision →delete_git_repo on cPanel MCP Server →remove_concept on MegaMemory → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →