List workflows in a repository
AI agents call gh_workflow_list to retrieve information from GitHub CLI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing workflows queries repository metadata to display available CI/CD workflows. This is a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal — an agent cannot cause harm by merely listing workflows.
From the tool's definition Tool name is 'gh_workflow_list' and description states 'List workflows in a repository' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List workflows in a repository. It is categorised as a Read tool in the GitHub CLI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub CLI MCP Server MCP server in PolicyLayer and add a rule for gh_workflow_list: 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 GitHub CLI MCP Server. Nothing to install.
gh_workflow_list 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 gh_workflow_list 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 gh_workflow_list. 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.
gh_workflow_list is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →