Get jobs for a specific workflow run
AI agents call get_workflow_run_jobs to retrieve information from GitHub Actions MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries data about workflow run jobs with no side effects. It follows the 'get' pattern typical of Read operations. While GitHub Actions workflows can execute code, this particular tool only fetches metadata about jobs, not triggering or modifying them. Blast radius is minimal—an agent could learn about job details but cannot execute, cancel, or modify workflows with this tool alone.
From the tool's definition Tool name is 'get_workflow_run_jobs' and description states 'Get jobs for a specific workflow run' — retrieves information about jobs without modifying state.
Attacks that exploit this kind of access
Get jobs for a specific workflow run. It is categorised as a Read tool in the GitHub Actions MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Actions MCP Server MCP server in PolicyLayer and add a rule for get_workflow_run_jobs: 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 Actions MCP Server. Nothing to install.
get_workflow_run_jobs 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 get_workflow_run_jobs 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 get_workflow_run_jobs. 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.
get_workflow_run_jobs is provided by the GitHub Actions MCP Server MCP server (onemarc/github-actions-mcp-server). 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 →