List system webhooks (requires admin privileges)
AI agents call admin_list_hooks to retrieve information from Forgejo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system webhook configurations, which are read-only queries with no side effects or data modification. However, severity is elevated to 'high' because webhooks often contain sensitive information such as secrets, authentication tokens, URLs pointing to internal systems, and callback configurations that could expose infrastructure details or enable further attacks if disclosed to an unauthorized…
From the tool's definition Tool name 'admin_list_hooks' and description 'List system webhooks (requires admin privileges)' indicate a read-only operation that retrieves webhook configuration data. The word 'list' and 'requires admin privileges' confirm this is a data retrieval action.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access admin_list_hooks 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 admin_list_hooks:
{
"version": "1",
"default": "deny",
"tools": {
"admin_list_hooks": {}
}
}admin_list_hooks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List system webhooks (requires admin privileges). It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.
Register the Forgejo MCP server in PolicyLayer and add a rule for admin_list_hooks: 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_list_hooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the admin_list_hooks 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_list_hooks. 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_list_hooks 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.