· ai-devtools
GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform
The release allows MCP-compatible tools such as Claude Code and Cursor to access GitLab's broader tool catalogue and invoke GitLab Duo Agent Platform agents and flows.
At the same time, GitLab is adding controls for governing those external agents, giving security teams visibility into which agents are being used, by whom, and against which projects. The generally available GitLab MCP server provides agents with access to GitLab capabilities through the Model Context Protocol.
New tools allow agents to discover groups, inspect individual CI/CD artifact files, and start or monitor GitLab Duo agents and flows. Administrators can also select which MCP toolsets are exposed, reducing unnecessary tools and the context they consume.
Giving an agent every available tool increases both context consumption and the number of actions the model could potentially take. Toolset selection provides a relatively simple form of least-privilege agent design.
GitLab.com also introduces MCP rate limits of 60 requests per minute for Free users and 600 for Premium and Ultimate users, with reconnects and retries counting towards the limit. One of the more significant additions is the ability to bring Externally Connected Agents into GitLab's AI Governance capabilities.
