Low Risk

forgejo_list_issues

List issues in a repository

How to control forgejo_list_issues ↓

What forgejo_list_issues does on Crow

AI agents call forgejo_list_issues to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why forgejo_list_issues needs a policy

This tool performs a read-only operation to retrieve and display issues from a repository. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal — an attacker could only enumerate issues, potentially revealing project information but causing no direct harm or state change.

From the tool's definition Tool name and description indicate it 'List issues in a repository' — a query operation that retrieves data without modification or side effects.

Documented attack patterns abuse exactly the kind of access forgejo_list_issues gives an agent:

How to control forgejo_list_issues

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for forgejo_list_issues:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "forgejo_list_issues": {}
  }
}

forgejo_list_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.