This record as markdown: /tools/kh0pper-crow/forgejo-repo-info.md
What forgejo_repo_info does on Crow
AI agents call forgejo_repo_info to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why forgejo_repo_info is rated Low
This tool retrieves repository metadata and details from a Forgejo instance. It performs a read-only operation with no capability to modify, delete, or execute actions. The blast radius of misuse is limited to information disclosure, which is low severity for repository metadata that is typically meant to be accessible.
From the tool's definition Tool name 'forgejo_repo_info' and description 'Get detailed info for one repository' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
The rule that runs forgejo_repo_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For forgejo_repo_info, this is the rule to start with:
forgejo_repo_info 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 Crow, apply this rule, and every forgejo_repo_info call is checked against it from then on.
Questions about forgejo_repo_info
Get detailed info for one repository. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for forgejo_repo_info: 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 Crow. Nothing to install.
forgejo_repo_info 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 forgejo_repo_info 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 forgejo_repo_info. 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.
forgejo_repo_info is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue