List workflow runs for a repository or specific workflow
AI agents call github_list_workflow_runs to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access github_list_workflow_runs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for github_list_workflow_runs:
{
"version": "1",
"default": "deny",
"tools": {
"github_list_workflow_runs": {}
}
}github_list_workflow_runs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.