// MCP TOOL REFERENCE

JENKINS TOOLS

14 tools from the Jenkins MCP Server, categorised by risk level.

// ALL 14 JENKINS TOOLS

READ 13 tools

Read get_build_console_output Get build console output Read get_build_history Get build history for a job Read get_build_logs Get build logs for a specific build Read get_build_parameters Get parameters used in a specific build Read get_build_status Get build status Read get_build_test_results Get test results for a specific build Read get_job_config Get Jenkins job configuration in XML format Read get_job_health Get health information for a Jenkins job Read get_job_statistics Get statistics for a Jenkins job Read get_job_status Get current status of a Jenkins job Read get_node_info Get information about Jenkins nodes/slaves Read get_queue_info Get information about items in the Jenkins queue Read list_jobs List all Jenkins jobs

EXECUTE 1 tools

Execute trigger_build Trigger a Jenkins build

// FAQ

How many tools does the Jenkins MCP server have? +

The Jenkins MCP server exposes 14 tools across 2 categories: Read, Execute.

How do I enforce policies on Jenkins tools? +

Route the Jenkins server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Jenkins tools fall into? +

Jenkins tools are categorised as Read (13), Execute (1). Each category has a recommended default policy.

Enforce policy on every Jenkins tool call.

Start from Jenkins, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.