github_list_workflow_runs

A read tool on the Github MCP server.

SERVERGithub SOURCEdkeeno/github-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about github_list_workflow_runs

What does the github_list_workflow_runs tool do? +

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.

How do I enforce a policy on github_list_workflow_runs? +

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.

What risk level is github_list_workflow_runs? +

github_list_workflow_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github_list_workflow_runs? +

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.

How do I block github_list_workflow_runs completely? +

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.

What MCP server provides github_list_workflow_runs? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Github's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.