List recent pipelines for a project. Filter by branch (ref) or status (running, pending, success, failed, canceled).
AI agents call list_pipelines to retrieve information from Mcp Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing pipeline data without side effects. It is a read-only operation analogous to listing or querying resources. The low severity reflects that exposing pipeline metadata poses minimal risk—no code execution, data modification, or resource destruction is involved.
From the tool's definition Tool name 'list_pipelines' and description 'List recent pipelines for a project' indicate a query/retrieval operation with filtering options (by branch/status). No modification, deletion, or execution of pipelines occurs.
Attacks that exploit this kind of access
List recent pipelines for a project. Filter by branch (ref) or status (running, pending, success, failed, canceled). It is categorised as a Read tool in the Mcp Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for list_pipelines: 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 Mcp Gitlab. Nothing to install.
list_pipelines 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 list_pipelines 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 list_pipelines. 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.
list_pipelines is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). 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 →