list_pipelines_tool
AI agents call list_pipelines_tool 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.
The tool name explicitly contains 'list_', a strong indicator of data querying with no side effects. Although the description is empty, context from sibling tools and conventional naming strongly suggest this retrieves or enumerates existing pipeline objects without modification. No evidence of write, execute, delete, or financial operations. Listing pipelines has low blast radius even if misused by an agent.
From the tool's definition Tool name 'list_pipelines_tool' indicates retrieval of pipeline data. Sibling tools on the GitLab MCP server include action-oriented tools like 'cancel_pipeline_tool' and 'create_merge_request_tool', which perform modifications.
Attacks that exploit this kind of access
list_pipelines_tool. 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_tool: 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_tool 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_tool 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_tool. 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_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →