View details about a workflow run
AI agents call gh_run_view to retrieve information from GitHub CLI 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 displays information about a GitHub Actions workflow run. 'View' indicates a read-only operation with no side effects — it queries and returns data without modifying any state.
From the tool's definition View details about a workflow run
Attacks that exploit this kind of access
View details about a workflow run. It is categorised as a Read tool in the GitHub CLI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub CLI MCP Server MCP server in PolicyLayer and add a rule for gh_run_view: 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 CLI MCP Server. Nothing to install.
gh_run_view 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 gh_run_view 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 gh_run_view. 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.
gh_run_view is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-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 →