get_issue_config

Get the issue config of a repository

SERVERForgejo SOURCEsqcows/forgejo-mcp

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/sqcows-forgejo-mcp/get-issue-config.md

WHAT IT DOES

What get_issue_config does on Forgejo

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

RISK

Why get_issue_config is rated Low

Retrieves repository configuration data without modifying or executing any operations.

From the tool's definition Get the issue config of a repository

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_issue_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_issue_config, this is the rule to start with:

get_issue_config Allowed

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

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

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

FAQ

Questions about get_issue_config

What does the get_issue_config tool do? +

Get the issue config of a repository. It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issue_config? +

Register the Forgejo MCP server in PolicyLayer and add a rule for get_issue_config: 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 Forgejo. Nothing to install.

What risk level is get_issue_config? +

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

Can I rate-limit get_issue_config? +

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

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

get_issue_config is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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