Get jobs for a specific pipeline.
AI agents call get_pipeline_jobs to retrieve information from GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries pipeline job information from GitLab CI/CD workflows. The use of 'get' combined with 'jobs' and the description stating it 'gets' (retrieves) jobs for a pipeline demonstrates a read-only operation with no side effects, modification, or code execution. This falls clearly under the Read category as it fetches existing data without altering system state.
From the tool's definition Tool name 'get_pipeline_jobs' and description 'Get jobs for a specific pipeline' indicate retrieval of existing pipeline job data without modification or execution of those jobs.
Attacks that exploit this kind of access
Get jobs for a specific pipeline. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_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 GitLab MCP Server. Nothing to install.
get_pipeline_jobs 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_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.
Set action: deny in the PolicyLayer policy for get_pipeline_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.
get_pipeline_jobs is provided by the GitLab MCP Server MCP server (skmprb/gitlab-clone-mcp-server). 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 →