remove_repo_flag
Remove a flag from a repository (instance admin only)
This record as markdown: /tools/sqcows-forgejo-mcp/remove-repo-flag.md
What remove_repo_flag does on Forgejo
AI agents use remove_repo_flag 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.
Why remove_repo_flag is rated Medium
Removes a metadata flag from a repository; reversible write action with admin-level blast radius.
From the tool's definition Remove a flag from a repository (instance admin only)
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs remove_repo_flag 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_repo_flag, this is the rule to start with:
remove_repo_flag 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every remove_repo_flag call is checked against it from then on.
Questions about remove_repo_flag
Remove a flag from a repository (instance admin only). 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 remove_repo_flag: 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.
remove_repo_flag 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_repo_flag 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_repo_flag. 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_repo_flag 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.
More on Forgejo, and thousands of servers like it.
This server
Across the catalogue