get_issue

Get one issue by its project-scoped IID.

Server GitLab MCP shahabmosavi/gitlab_mcp
Category Read
Risk class Low
Parameters 00 required

What get_issue does on GitLab MCP

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

Why get_issue needs a policy

This tool retrieves a single issue object from GitLab by its identifier. It performs a query operation without creating, modifying, deleting, or executing any action. The blast radius of misuse is minimal—an attacker could only access information about an issue they may already have visibility to, with no ability to alter state or trigger external operations.

From the tool's definition Tool name 'get_issue' and description 'Get one issue by its project-scoped IID' indicate a retrieval operation with no modification or side effects.

Questions about get_issue

What does the get_issue tool do? +

Get one issue by its project-scoped IID. It is categorised as a Read tool in the GitLab MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issue? +

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

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 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 completely? +

Set action: deny in the PolicyLayer 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 GitLab MCP server (shahabmosavi/gitlab_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.