// SCAN REPORT

Jenkins Http

32 tools. 12 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

12 can modify or destroy data

20 read-only

32 tools total

Community server · catalogue entry verified 03/07/2026

How to control Jenkins Http ↓

TOOL MAP

What Jenkins Http exposes to your agents

Read (20) Write / Execute (10) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Jenkins Http tools

Destructive · High jenkins_cancel_queue_item Cancelling a queue item irreversibly removes it from the Jenkins build queue. Destructive · High jenkins_delete_job The tool performs an irreversible deletion operation on Jenkins jobs. Execute · Medium jenkins_cancel_workspace_bundle_download This tool triggers an external operation (cancelling a running process) on the Jenkins server. Execute · High jenkins_start_workspace_bundle_download This tool executes a multi-step operation (download, extract, cleanup) that has side effects on the Jenkins workspace and filesystem.

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

POLICY

How to control Jenkins Http

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

Deny destructive operations

{
  "jenkins_cancel_queue_item": {
    "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_build": {
    "limits": [
      {
        "counter": "jenkins_get_build_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 Jenkins Http — 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 JENKINS HTTP →

Instant setup, no code required.

FULL CATALOGUE

All 32 Jenkins Http tools

DESTRUCTIVE 2 tools

Destructive jenkins_cancel_queue_item Cancel a Jenkins queue item. Requires JENKINS_MCP_ENABLE_WRITES=1. Destructive jenkins_delete_job Delete a job. Requires write, job-config, and delete flags.

EXECUTE 5 tools

Execute jenkins_cancel_workspace_bundle_download Request cancellation of a running workspace bundle operation. Execute jenkins_start_workspace_bundle_download Start async workspace zip download, extraction, cleanup, and console log save. Execute jenkins_stop_build Stop a running build. Requires JENKINS_MCP_ENABLE_WRITES=1. Execute jenkins_trigger_build Trigger a non-parameterized job build. Requires JENKINS_MCP_ENABLE_WRITES=1. Execute jenkins_trigger_build_with_parameters Trigger a parameterized job build. Requires JENKINS_MCP_ENABLE_WRITES=1.

WRITE 5 tools

Write jenkins_copy_job Copy a top-level job. Requires write and job-config flags. Write jenkins_create_job Create a top-level job from config.xml. Requires write and job-config flags. Write jenkins_disable_job Disable a job. Requires JENKINS_MCP_ENABLE_WRITES=1. Write jenkins_enable_job Enable a job. Requires JENKINS_MCP_ENABLE_WRITES=1. Write jenkins_update_job_config Replace job config.xml. Requires write and job-config flags.

READ 20 tools

Read jenkins_get_build Get a build by number or Jenkins permalink such as lastBuild. Read jenkins_get_build_artifacts List artifacts exported on a build JSON API response. Read jenkins_get_build_log Get consoleText for a build, truncated by JENKINS_MCP_MAX_LOG_BYTES. Read jenkins_get_job Get one job by Jenkins job path. Nested paths use slash-separated names or a list. Read jenkins_get_job_config Read job config.xml. Jenkins may redact secrets without Configure permission. Read jenkins_get_json GET a relative Jenkins JSON API path. Rejects external URLs and traversal. Read jenkins_get_node Get one Jenkins computer/node by name. Use (built-in) for the built-in node. Read jenkins_get_queue_item Get one Jenkins queue item by ID. Read jenkins_get_test_report Get /testReport/api/json when a test-report plugin such as JUnit provides it. Read jenkins_get_view Get one Jenkins view by name. Read jenkins_get_workspace_bundle_status Get download/extract/log progress, bytes, speed, paths, and final status. Read jenkins_health Return a small health snapshot from top-level Jenkins JSON and version headers. Read jenkins_list_builds List recent builds for a job. Read jenkins_list_jobs List jobs visible to the Jenkins user. Read jenkins_list_nodes List Jenkins computers/nodes visible to the user. Read jenkins_list_plugins List installed Jenkins plugins visible through pluginManager/api/json. Read jenkins_list_queue List visible Jenkins queue items. Read jenkins_list_views List Jenkins views visible to the user. Read jenkins_version Return Jenkins version from the X-Jenkins response header. Read jenkins_whoami Return the authenticated Jenkins identity from /whoAmI/api/json.

EXPLORE

Related servers

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

FAQ

Questions about Jenkins Http

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

Yes. The Jenkins Http server exposes 2 destructive tools including jenkins_cancel_queue_item, 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 Jenkins Http? +

The Jenkins Http server has 5 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 Jenkins Http.

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

32 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Jenkins Http? +

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

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

ENFORCE POLICY ON JENKINS HTTP →

Instant setup, no code required.

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