List pipelines for a repository with optional filtering. Returns pipeline metadata including status, commit info, and timing. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit.
AI agents call list_pipelines to retrieve information from Woodpecker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pipeline information without side effects. It returns metadata about existing pipelines (status, commit info, timing) but does not create, modify, delete, or execute anything. This is a straightforward Read operation with minimal security risk—an agent listing pipelines can view CI/CD status but cannot alter pipelines or trigger unintended operations.
From the tool's definition Tool name is 'list_pipelines' and description states it 'List pipelines for a repository' and 'Returns pipeline metadata'. The verb 'List' and action of returning metadata are characteristic of read-only operations.
Documented attack patterns abuse exactly the kind of access list_pipelines gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Woodpecker, and nothing reaches the server without passing your rules. This is the rule we recommend for list_pipelines:
{
"version": "1",
"default": "deny",
"tools": {
"list_pipelines": {}
}
}list_pipelines is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List pipelines for a repository with optional filtering. Returns pipeline metadata including status, commit info, and timing. If required information is not provided, use the git command or any available tool to get more context about the current commit, the repository, or the author of the commit. It is categorised as a Read tool in the Woodpecker MCP Server, which means it retrieves data without modifying state.
Register the Woodpecker MCP server in PolicyLayer and add a rule for list_pipelines: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Woodpecker. Nothing to install.
list_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_pipelines rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_pipelines. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_pipelines is provided by the Woodpecker MCP server (j04n-f/woodpecker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Woodpecker, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Woodpecker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.