github_get_workflow_logs
Download the logs zip for a workflow run and return the tail.
This record as markdown: /tools/dkeeno-github-mcp-server/github-get-workflow-logs.md
What github_get_workflow_logs does on Github
AI agents call github_get_workflow_logs 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_logs is rated Low
This tool retrieves and reads workflow execution logs, which are informational artifacts. It has no side effects on repositories, workflows, code, or infrastructure. The action is purely querying and reading existing data that has already been generated by GitHub Actions. No data is created, modified, deleted, or any external operations are triggered.
From the tool's definition Tool name includes 'get' and description states 'Download the logs zip for a workflow run and return the tail' — retrieval and reading of existing logs without modification.
Attacks that exploit this kind of access
The rule that runs github_get_workflow_logs 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_logs, this is the rule to start with:
github_get_workflow_logs 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_logs call is checked against it from then on.
Questions about github_get_workflow_logs
Download the logs zip for a workflow run and return the tail. 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_logs: 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_logs 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_logs 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_logs. 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_logs 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