forgejo_list_issues

List issues in a 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/forgejo-list-issues.md

WHAT IT DOES

What forgejo_list_issues does on Crow

AI agents call forgejo_list_issues 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 forgejo_list_issues is rated Low

This tool performs a read-only query operation that retrieves existing issues from a repository. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only access issue information the caller already has permissions to view.

From the tool's definition Tool name and description indicate a list operation: 'List issues in a repository' retrieves issue data without modification or destructive action.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

forgejo_list_issues Allowed

forgejo_list_issues 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": {
    "forgejo_list_issues": {}
  }
}

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 forgejo_list_issues call is checked against it from then on.

FAQ

Questions about forgejo_list_issues

What does the forgejo_list_issues tool do? +

List issues in a 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 forgejo_list_issues? +

Register the Crow MCP server in PolicyLayer and add a rule for forgejo_list_issues: 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 forgejo_list_issues? +

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

Can I rate-limit forgejo_list_issues? +

Yes. Add a rate_limit block to the forgejo_list_issues 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 forgejo_list_issues completely? +

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

forgejo_list_issues 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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