Download and extract the log files for a GitHub Actions workflow run.
AI agents call github_workflow_get_run_logs to retrieve information from Promethean OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log data from GitHub Actions without creating, modifying, deleting, or executing any code. It has no side effects on the GitHub repository or workflow runs themselves.
From the tool's definition Tool name and description indicate 'Download and extract the log files' — a retrieval operation with no modification or execution of external systems. The action is read-only on stored GitHub workflow logs.
Attacks that exploit this kind of access
Download and extract the log files for a GitHub Actions workflow run. It is categorised as a Read tool in the Promethean OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Promethean OS MCP server in PolicyLayer and add a rule for github_workflow_get_run_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 Promethean OS MCP. Nothing to install.
github_workflow_get_run_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_workflow_get_run_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_workflow_get_run_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_workflow_get_run_logs is provided by the Promethean OS MCP server (octave-commons/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 →