list_pipeline_trigger_jobs

List trigger jobs (bridges) in a pipeline

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/list-pipeline-trigger-jobs.md

What list_pipeline_trigger_jobs does on Gitlab Mcp

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

Why list_pipeline_trigger_jobs is rated Low

This tool retrieves and queries trigger job data from a GitLab pipeline. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an attacker could only view pipeline job information they might already have access to. No data is changed, no code is executed, and no resources are consumed beyond normal API quota.

From the tool's definition 'List trigger jobs (bridges) in a pipeline' — the verb 'list' and the action of retrieving pipeline job information indicates a read-only query operation with no side effects.

Questions about list_pipeline_trigger_jobs

What does the list_pipeline_trigger_jobs tool do? +

List trigger jobs (bridges) in a pipeline. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_pipeline_trigger_jobs? +

Register the Gitlab MCP server in PolicyLayer and add a rule for list_pipeline_trigger_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. Nothing to install.

What risk level is list_pipeline_trigger_jobs? +

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

Can I rate-limit list_pipeline_trigger_jobs? +

Yes. Add a rate_limit block to the list_pipeline_trigger_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 list_pipeline_trigger_jobs completely? +

Set action: deny in the PolicyLayer policy for list_pipeline_trigger_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 list_pipeline_trigger_jobs? +

list_pipeline_trigger_jobs is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

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.