This record as markdown: /tools/sqcows-forgejo-mcp/get-release-by-tag.md
What get_release_by_tag does on Forgejo
AI agents call get_release_by_tag to retrieve information from Forgejo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_release_by_tag is rated Low
This tool retrieves metadata about a GitHub release identified by a tag. It performs a read-only query operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only access release information that would typically be public or already accessible to the authenticated user.
From the tool's definition Tool name 'get_release_by_tag' and description 'Get a release by tag name' indicate a retrieval operation with no side effects. This queries existing release data without modification.
Attacks that exploit this kind of access
The rule that runs get_release_by_tag 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 get_release_by_tag, this is the rule to start with:
get_release_by_tag is read-only, so it stays allowed. 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 get_release_by_tag call is checked against it from then on.
Questions about get_release_by_tag
Get a release by tag name. 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 get_release_by_tag: 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.
get_release_by_tag 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 get_release_by_tag 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 get_release_by_tag. 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.
get_release_by_tag 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