List workflow runs in a GitHub repository
AI agents call list-workflow-runs to retrieve information from GitHub Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists existing workflow run data from a GitHub repository. It does not create, modify, delete, or execute any operations—it only queries and returns information. The blast radius of misuse is minimal: an attacker could discover workflow details or secrets visible in logs, but cannot modify repository state or trigger actions. This is classified as a Read operation with low severity.
From the tool's definition Tool name 'list-workflow-runs' and description 'List workflow runs in a GitHub repository' indicate a retrieval operation with no side effects. This follows the Read pattern: retrieves or queries data without modification.
Attacks that exploit this kind of access
List workflow runs in a GitHub repository. It is categorised as a Read tool in the GitHub Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Enterprise MCP Server MCP server in PolicyLayer and add a rule for 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 Enterprise MCP Server. Nothing to install.
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 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 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.
list-workflow-runs is provided by the GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-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 →