Mcp Jenkins

38 tools. 16 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

16 can modify or destroy data
22 read-only
38 tools total

Community server · catalogue entry verified 28/06/2026

How to control Mcp Jenkins ↓

What Mcp Jenkins exposes to your agents

Read (22) Write / Execute (13) Destructive / Financial (3)
Critical Risk

The most dangerous Mcp Jenkins tools

16 of Mcp Jenkins's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Mcp Jenkins

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

Deny destructive operations
{
  "jenkins_cancel_queue": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

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

Rate limit write operations
{
  "jenkins_copy_job": {
    "limits": [
      {
        "counter": "jenkins_copy_job_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "jenkins_get_artifact": {
    "limits": [
      {
        "counter": "jenkins_get_artifact_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Mcp Jenkins — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON MCP JENKINS →

Instant setup, no code required.

All 38 Mcp Jenkins tools

READ 22 tools
Read jenkins_get_artifact Download a specific artifact from a build (returns base64-encoded content) Read jenkins_get_build_changes Get Git commits/changes for a build Read jenkins_get_build_status Get detailed status of a specific build number for a job Read jenkins_get_console_log Get console log output from a build. Returns both a snippet and full log. Read jenkins_get_job_config Get job configuration XML Read jenkins_get_job_parameters Get the parameter definitions for a parameterised Jenkins job — names, types, defaults, and choices Read jenkins_get_job_status Get the status of the last build for a specific job Read jenkins_get_node Get detailed information about a specific Jenkins node/agent Read jenkins_get_pipeline_stages Get pipeline stages and their status for a build Read jenkins_get_plugins List all installed Jenkins plugins Read jenkins_get_queue Get the current build queue showing pending builds Read jenkins_get_recent_builds Get recent builds for a job with their status and metadata Read jenkins_get_system_info Get Jenkins system information Read jenkins_get_test_results Get test results for a build (pass/fail counts, test suites) Read jenkins_get_version Get Jenkins version Read jenkins_get_view Get details and job list for a specific Jenkins view Read jenkins_list_artifacts List all artifacts produced by a specific build Read jenkins_list_instances List all configured Jenkins instances with their names and URLs Read jenkins_list_jobs List all Jenkins jobs with their names and URLs Read jenkins_list_nodes List all Jenkins nodes/agents and their status Read jenkins_list_views List all Jenkins views with their jobs Read jenkins_search_jobs Search for Jenkins jobs by name (case-insensitive substring match)

Related servers

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

Questions about Mcp Jenkins

Can an AI agent delete data through the Mcp Jenkins MCP server? +

Yes. The Mcp Jenkins server exposes 3 destructive tools including jenkins_cancel_queue, jenkins_delete_build, jenkins_delete_job. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mcp Jenkins? +

The Mcp Jenkins server has 6 write tools including jenkins_copy_job, jenkins_create_job, jenkins_disable_job. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Jenkins.

How many tools does the Mcp Jenkins MCP server expose? +

38 tools across 4 categories: Destructive, Execute, Read, Write. 22 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Mcp Jenkins? +

Register the Mcp Jenkins 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 Mcp Jenkins tool call.

Deterministic rules across all 38 Mcp Jenkins tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

38 Mcp Jenkins tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.