获取 GitLab 流水线状态
AI agents call get_pipeline_status to retrieve information from GitLab Pipeline MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of a GitLab pipeline, which is a read-only operation. It queries existing pipeline information and returns state data (pending, running, success, failed, etc.) with no side effects. The context of sibling tools (cancel_pipeline, trigger_pipeline) that perform state changes further confirms this is purely informational.
From the tool's definition Tool name 'get_pipeline_status' and description 'get/retrieve GitLab pipeline status' indicate a query operation that retrieves pipeline state information without modifying any data.
Attacks that exploit this kind of access
获取 GitLab 流水线状态. It is categorised as a Read tool in the GitLab Pipeline MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab Pipeline MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_status: 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 GitLab Pipeline MCP Server. Nothing to install.
get_pipeline_status 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 get_pipeline_status 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 get_pipeline_status. 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.
get_pipeline_status is provided by the GitLab Pipeline MCP Server MCP server (wqhui/mcp-gitlab). 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 →