// SCAN REPORT

GoCD MCP Server

18 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

3 can modify or destroy data

15 read-only

18 tools total

Community server · catalogue entry verified 30/06/2026

How to control GoCD MCP Server ↓

TOOL MAP

What GoCD MCP Server exposes to your agents

Read (15) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous GoCD MCP Server tools

Destructive · High cancel_stage Cancelling a running stage and all its jobs is an irreversible action — the in-progress execution is terminated immediately and cannot be undone. Execute · High trigger_pipeline This tool triggers automated pipeline execution, which can initiate builds, deployments, or other CI/CD operations. Execute · High trigger_stage This tool executes CI/CD pipeline stages, which can have significant consequences (deployments, releases, infrastructure changes).

3 of GoCD MCP Server's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GoCD MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and GoCD MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "cancel_stage": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "analyze_job_failures": {
    "limits": [
      {
        "counter": "analyze_job_failures_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GoCD MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOCD →

Instant setup, no code required.

FULL CATALOGUE

All 18 GoCD MCP Server tools

DESTRUCTIVE 1 tools

Destructive cancel_stage Cancel a running stage and all its jobs immediately. Use this to stop a long-running stage, abort a deployment

EXECUTE 2 tools

Execute trigger_pipeline Schedule and trigger a new pipeline run immediately, optionally with custom environment variables. Use this to Execute trigger_stage Manually trigger or rerun a specific stage in a pipeline. Use this to retry a failed stage, run a manual appro

READ 15 tools

Read analyze_job_failures Comprehensive analysis of all failures and errors for a job. Use this when asked to Read get_job_artifact Download and read a specific artifact file from a job. Use this to retrieve specific files like test reports, Read get_job_console Get the complete console log output for a specific job run. Use this to see build logs, compilation errors, ru Read get_job_history Get the execution history of a specific job across multiple pipeline runs. Use this to see historical trends, Read get_job_instance Get details of a specific job run including state (Scheduled, Building, Completed), result (Passed, Failed, Ca Read get_pipeline_history Get the run history of a pipeline with pagination support. Use this to see recent pipeline runs, find the late Read get_pipeline_instance Get comprehensive details of a specific pipeline run including build cause (what triggered it), materials (git Read get_pipeline_status Get the current status of a pipeline including pause state (paused or not), lock status (locked by another run Read get_stage_instance Get details of a specific stage run including all jobs, their states (Scheduled, Building, Completed), results Read list_job_artifacts List all artifacts (files and folders) produced by a job, including test reports (JUnit XML), coverage reports Read list_pipelines List all pipelines in the GoCD server with their groups and pause status. Use this to discover available pipel Read parse_gocd_url Parse a GoCD URL to extract pipeline, stage, and job information. Use this FIRST when the user provides a GoCD Read parse_junit_xml Parse a JUnit XML test report to extract structured test results, failures, and errors. Use this when analyzin Read pause_pipeline Pause a pipeline to prevent automatic scheduling and triggering. Use this to temporarily disable a pipeline du Read unpause_pipeline Unpause a previously paused pipeline to resume automatic scheduling and triggering. Use this to re-enable a pi

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about GoCD MCP Server

Can an AI agent delete data through the GoCD MCP Server MCP server? +

Yes. The GoCD MCP Server server exposes 1 destructive tools including cancel_stage. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the GoCD MCP Server MCP server expose? +

18 tools across 3 categories: Destructive, Execute, Read. 15 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on GoCD MCP Server? +

Register the GoCD MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GoCD MCP Server tool call.

Deterministic rules across all 18 GoCD MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOCD →

Instant setup, no code required.

18 GoCD MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.