get_pipeline_failed_jobs

GitLabパイプラインで失敗したジョブのコンソール出力を取得

Server Https://github Com/owayo/gitlab owayo/gitlab-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_pipeline_failed_jobs does on Https://github Com/owayo/gitlab

AI agents call get_pipeline_failed_jobs to retrieve information from Https://github Com/owayo/gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_pipeline_failed_jobs needs a policy

This tool only retrieves and reads existing pipeline failure data and console logs from GitLab. It performs no write, delete, code execution, or financial operations. The action is a simple query/fetch operation with no side effects, which is characteristic of the Read category. The low severity reflects that accessing CI/CD logs poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_pipeline_failed_jobs' and description 'GitLabパイプラインで失敗したジョブのコンソール出力を取得' (retrieve console output of failed jobs in GitLab pipeline) indicate a retrieval operation with no modification or execution of external systems.

Questions about get_pipeline_failed_jobs

What does the get_pipeline_failed_jobs tool do? +

GitLabパイプラインで失敗したジョブのコンソール出力を取得. It is categorised as a Read tool in the Https://github Com/owayo/gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pipeline_failed_jobs? +

Register the Https://github Com/owayo/gitlab MCP server in PolicyLayer and add a rule for get_pipeline_failed_jobs: 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 Https://github Com/owayo/gitlab. Nothing to install.

What risk level is get_pipeline_failed_jobs? +

get_pipeline_failed_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pipeline_failed_jobs? +

Yes. Add a rate_limit block to the get_pipeline_failed_jobs 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.

How do I block get_pipeline_failed_jobs completely? +

Set action: deny in the PolicyLayer policy for get_pipeline_failed_jobs. 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.

What MCP server provides get_pipeline_failed_jobs? +

get_pipeline_failed_jobs is provided by the Https://github Com/owayo/gitlab MCP server (owayo/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.