gitlab_pipelines

What gitlab_pipelines does on Yaver

AI agents call gitlab_pipelines to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameters from the server's own tool schema.

Why gitlab_pipelines is rated Low

This tool performs a read-only operation—listing existing CI/CD pipelines. It retrieves data about pipeline status and history without side effects. While pipelines can reveal information about deployment processes, the tool itself does not trigger execution, modify configurations, or change state. The blast radius is minimal as it only returns information available to authenticated users with pipeline visibility.

From the tool's definition Tool name 'gitlab_pipelines' and description 'List GitLab CI/CD pipelines' indicate a query operation that retrieves pipeline data without modifying, deleting, or executing code.

Risk signalsAccepts file system path (directory)

The rule that runs gitlab_pipelines safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_pipelines, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_pipelines": {}
  }
}

Questions about gitlab_pipelines