List recent workflow runs
AI agents call gh_run_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.
The tool lists/retrieves workflow run records from GitHub. This is a read-only operation with no side effects, similar to querying run history. Minimal blast radius if misused.
From the tool's definition List recent workflow runs
Attacks that exploit this kind of access
List recent workflow runs. 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_run_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_run_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_run_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_run_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_run_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 →