admin_remove_quota_group_rule
Remove a rule from a quota group (requires admin privileges)
This record as markdown: /tools/sqcows-forgejo-mcp/admin-remove-quota-group-rule.md
What admin_remove_quota_group_rule does on Forgejo
AI agents call admin_remove_quota_group_rule 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.
Why admin_remove_quota_group_rule is rated Critical
Irreversibly removes quota rules, disabling resource limits and preventing undo without admin intervention.
From the tool's definition Remove a rule from a quota group; irreversible deletion of quota enforcement
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_remove_quota_group_rule 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 admin_remove_quota_group_rule, this is the rule to start with:
admin_remove_quota_group_rule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every admin_remove_quota_group_rule call is checked against it from then on.
Questions about admin_remove_quota_group_rule
Remove a rule from a quota group (requires admin privileges). 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.
Register the Forgejo MCP server in PolicyLayer and add a rule for admin_remove_quota_group_rule: 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.
admin_remove_quota_group_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the admin_remove_quota_group_rule 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 admin_remove_quota_group_rule. 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.
admin_remove_quota_group_rule 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.
Across the catalogue