github_get_workflow_run
Get details for a single workflow run, including job-level status.
This record as markdown: /tools/dkeeno-github-mcp-server/github-get-workflow-run.md
What github_get_workflow_run does on Github
AI agents call github_get_workflow_run 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_get_workflow_run is rated Low
This tool retrieves and queries workflow run information from GitHub Actions. It performs a read-only operation that returns status and details about an already-executed workflow. There are no side effects, no code execution, no data modification, and no irreversible actions.
From the tool's definition Tool name 'github_get_workflow_run' and description 'Get details for a single workflow run, including job-level status' indicate retrieval of workflow execution metadata without modification or execution of workflows.
Attacks that exploit this kind of access
The rule that runs github_get_workflow_run 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_get_workflow_run, this is the rule to start with:
github_get_workflow_run 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_get_workflow_run call is checked against it from then on.
Questions about github_get_workflow_run
Get details for a single workflow run, including job-level status. 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_get_workflow_run: 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_get_workflow_run 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_get_workflow_run 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_get_workflow_run. 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_get_workflow_run 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