15 tools. 3 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (cancel_queue_item, stop_build) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Execute tools (build_item) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Jenkins. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @mcp-server-jenkins cancel_queue_item:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
get_all_items:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Jenkins server exposes 2 destructive tools including cancel_queue_item, stop_build. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
15 tools across 3 categories: Destructive, Execute, Read. 12 are read-only. 3 can modify, create, or delete data.
One line change. Instead of running the Jenkins server directly, prefix it with Intercept: intercept -c jenkins.yaml -- npx -y @@mcp-server-jenkins. Download a pre-built policy from policylayer.com/policies/jenkins and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init