// MCP TOOL REFERENCE

WOODPECKER TOOLS

7 tools from the Woodpecker MCP Server, categorised by risk level.

// ALL 7 WOODPECKER TOOLS

READ 7 tools

Read get_pipeline Get detailed information about a specific pipeline, including workflows, steps, and error details. If requi... Read get_pipeline_config Get the configuration files (.woodpecker.yml) used by a specific pipeline. Essential understanding pipeline... Read get_repository_by_id Get repository details by ID. Useful when you already have the repo ID from other operations and need repos... Read get_step_logs Get logs for a specific pipeline step. Useful for debugging individual step failures or examining step output. Read list_pipelines List pipelines for a repository with optional filtering. Returns pipeline metadata including status, commit... Read list_repositories List all repositories with optional filtering. Returns repository metadata including configuration, status,... Read search_repository Find a repository by its full name (owner/repo format). Returns repository details including ID, URLs, and ...

// FAQ

How many tools does the Woodpecker MCP server have? +

The Woodpecker MCP server exposes 7 tools across 1 categories: Read.

How do I enforce policies on Woodpecker tools? +

Route the Woodpecker 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 Woodpecker tools fall into? +

Woodpecker tools are categorised as Read (7). Each category has a recommended default policy.

Enforce policy on every Woodpecker tool call.

Start from Woodpecker, 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.