get_issue

// WHEN AI AGENTS USE THIS TOOL

AI agents call get_issue to retrieve information from MCP Gitlab without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON GET_ISSUE

Even though get_issue only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

mcp-gitlab.yaml

tools:
  get_issue:
    rules:
      - action: allow

See the full MCP Gitlab policy for all 30 tools.

// DETAILS

Tool Name get_issue

Category Read

MCP Server MCP Gitlab MCP Server

Risk Level Low

// MORE MCP GITLAB TOOLS

Write create_issue Write create_issue_note Write create_merge_request Write create_mr_note Write update_issue Write update_merge_request Read Cross-platform Read get_group

View all 30 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like get_issue have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the get_issue tool do? +

Get issue details. It is categorised as a Read tool in the MCP Gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issue? +

Add a rule in your Intercept YAML policy under the tools section for get_issue. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MCP Gitlab MCP server.

What risk level is get_issue? +

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

Can I rate-limit get_issue? +

Yes. Add a rate_limit block to the get_issue rule in your Intercept 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 completely? +

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

get_issue is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on MCP Gitlab