gitea_repo_info

Get detailed info for one repository

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/gitea-repo-info.md

WHAT IT DOES

What gitea_repo_info does on Crow

AI agents call gitea_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.

RISK

Why gitea_repo_info is rated Low

This tool retrieves information about a repository—a pure read operation with no side effects, no code execution, and no data modification capability. The blast radius is minimal since it only exposes repository metadata that would typically be accessible to authorized users anyway.

From the tool's definition Tool name 'gitea_repo_info' and description 'Get detailed info for one repository' indicate a read-only retrieval operation that queries metadata about a git repository without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitea_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 gitea_repo_info, this is the rule to start with:

gitea_repo_info Allowed

gitea_repo_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitea_repo_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every gitea_repo_info call is checked against it from then on.

FAQ

Questions about gitea_repo_info

What does the gitea_repo_info tool do? +

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.

How do I enforce a policy on gitea_repo_info? +

Register the Crow MCP server in PolicyLayer and add a rule for gitea_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.

What risk level is gitea_repo_info? +

gitea_repo_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gitea_repo_info? +

Yes. Add a rate_limit block to the gitea_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.

How do I block gitea_repo_info completely? +

Set action: deny in the PolicyLayer policy for gitea_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.

What MCP server provides gitea_repo_info? +

gitea_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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →