List releases of a repository
AI agents call list_releases 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 queries and returns release information from a repository without creating, modifying, or deleting any data. It is a straightforward read operation similar to list or fetch operations. The low severity reflects minimal risk even if misused by an AI agent, as listing releases poses no operational or security threat.
From the tool's definition Tool name 'list_releases' and description 'List releases of a repository' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_releases 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 list_releases:
{
"version": "1",
"default": "deny",
"tools": {
"list_releases": {}
}
}list_releases 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 releases of a repository. 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 list_releases: 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.
list_releases 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 list_releases 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 list_releases. 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.
list_releases 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.