github_list_workflow_runs
A read tool on the Github MCP server.
This record as markdown: /tools/dkeeno-github-mcp-server/github-list-workflow-runs.md
What github_list_workflow_runs does on Github
AI agents call github_list_workflow_runs to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github_list_workflow_runs is rated Low
This tool retrieves and displays workflow run information from GitHub without modifying, executing, or deleting any data. It follows the pattern of Read category tools (list, get, fetch). The low severity reflects that listing workflow runs poses minimal risk—it merely exposes existing metadata that an authenticated user can already access.
From the tool's definition Tool name 'github_list_workflow_runs' indicates a query/listing operation. The verb 'list' is a retrieval action with no side effects. No description provided, but the naming convention is clear and consistent with read-only operations.
Attacks that exploit this kind of access
The rule that runs github_list_workflow_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_list_workflow_runs, this is the rule to start with:
github_list_workflow_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every github_list_workflow_runs call is checked against it from then on.
Questions about github_list_workflow_runs
github_list_workflow_runs is a read tool on the Github MCP server. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.
Register the Github MCP server in PolicyLayer and add a rule for github_list_workflow_runs: 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. Nothing to install.
github_list_workflow_runs 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 github_list_workflow_runs 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 github_list_workflow_runs. 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.
github_list_workflow_runs is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
This server
Across the catalogue