github_list_workflow_runs

List workflow runs for a repository or specific workflow

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/github-list-workflow-runs.md

WHAT IT DOES

What github_list_workflow_runs does on Sage MCP

AI agents call github_list_workflow_runs to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_list_workflow_runs is rated Low

The tool retrieves and queries workflow run data from a GitHub repository without performing any side effects, modifications, or triggering execution of workflows. It is purely informational, making it a Read category risk with low severity since it exposes workflow metadata that may be available to authenticated users anyway.

From the tool's definition Tool name includes 'list' and description states 'List workflow runs' with no mention of modification, deletion, or execution capabilities. This is a data retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_list_workflow_runs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, 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 Allowed

github_list_workflow_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_list_workflow_runs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every github_list_workflow_runs call is checked against it from then on.

FAQ

Questions about github_list_workflow_runs

What does the github_list_workflow_runs tool do? +

List workflow runs for a repository or specific workflow. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_list_workflow_runs? +

Register the Sage 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 Sage MCP. 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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →