Get repository details by ID. Useful when you already have the repo ID from other operations and need repository context.
AI agents call get_repository_by_id 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 repository metadata/context by ID. It performs a simple lookup of existing data with no capability to modify, delete, or execute operations. The sibling tools on the server (list_pipelines, get_pipeline, get_step_logs, etc.) are also read-focused diagnostic utilities, consistent with the server's purpose of debugging and analyzing CI/CD pipelines.
From the tool's definition Tool name 'get_repository_by_id' and description 'Get repository details by ID' indicate a retrieval operation with no side effects. The phrase 'get repository details' is a classic read operation that queries and returns existing data without modification.
Documented attack patterns abuse exactly the kind of access get_repository_by_id 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 get_repository_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_repository_by_id": {}
}
}get_repository_by_id 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.
Get repository details by ID. Useful when you already have the repo ID from other operations and need repository context. 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 get_repository_by_id: 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.
get_repository_by_id 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 get_repository_by_id 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 get_repository_by_id. 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.
get_repository_by_id 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.