get_gitlab_issue
AI agents call get_gitlab_issue to retrieve information from DCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong signal for read-only operations that retrieve data. Given the sibling tools on this server (which include both read and write operations), and the absence of any language suggesting modification, deletion, or side effects, this tool most likely retrieves GitLab issue information.
From the tool's definition Tool name 'get_gitlab_issue' indicates a retrieval operation (get prefix). The description is empty, which reduces confidence slightly, but the naming convention and context within a server that includes read operations like 'download_dci_file' and…
Attacks that exploit this kind of access
get_gitlab_issue. It is categorised as a Read tool in the DCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DCI MCP Server MCP server in PolicyLayer and add a rule for get_gitlab_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 DCI MCP Server. Nothing to install.
get_gitlab_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_gitlab_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.
Set action: deny in the PolicyLayer policy for get_gitlab_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.
get_gitlab_issue is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →