List recent CI/CD pipelines for a GitLab project. Args: project_id: Project ID or URL-encoded path. limit: Max pipelines to return (default 10).
AI agents call gitlab_list_pipelines to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries GitLab to retrieve information about existing CI/CD pipelines. It has no side effects, does not modify state, and does not trigger or execute any pipelines. It is purely a data retrieval operation, fitting the Read category. Severity is low because listing pipeline metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List recent CI/CD pipelines'. The function retrieves pipeline data without modifying, deleting, or executing any operations. Arguments are project_id and limit—purely query parameters.
Documented attack patterns abuse exactly the kind of access gitlab_list_pipelines gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_list_pipelines:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_list_pipelines": {}
}
}gitlab_list_pipelines is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List recent CI/CD pipelines for a GitLab project. Args: project_id: Project ID or URL-encoded path. limit: Max pipelines to return (default 10). It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate MCP server in PolicyLayer and add a rule for gitlab_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 autoMate. Nothing to install.
gitlab_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 gitlab_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 gitlab_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.
gitlab_list_pipelines is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.