gitea_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/gitea-list-issues.md

What gitea_list_issues does on Crow

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

Why gitea_list_issues is rated Low

This tool performs a read-only operation - it retrieves and displays issues from a repository without any side effects. It does not create, modify, delete, or execute code. The blast radius is minimal since listing issues cannot cause unintended damage; at worst, an AI agent could retrieve sensitive issue information it shouldn't access, which is a data confidentiality concern rather than a destructive risk.

From the tool's definition Tool name 'gitea_list_issues' and description 'List issues in a repository' indicate a retrieval operation that queries data without modifying or deleting it.

Questions about gitea_list_issues

What does the gitea_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 gitea_list_issues? +

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

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

Can I rate-limit gitea_list_issues? +

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

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

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

More on Crow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.