actions_list

Tools for listing GitHub Actions resources. Use this tool to list workflows in a repository, or list workflow runs, jobs, and artifacts for a specific workflow or workflow run.

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/actions-list.md

WHAT IT DOES

What actions_list does on GitHub

AI agents call actions_list 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.

Parameter	Type	Required	Description
`page`	number	—	Page number for pagination (default: 1)
`repo`	string	—	Repository name
`owner`	string	—	Repository owner
`method`	string	—	The action to perform
`per_page`	number	—	Results per page for pagination (default: 30, max: 100)
`resource_id`	string	—	The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID: - Do not provide any resource ID for
`workflow_jobs_filter`	object	—	Filters for workflow jobs. ONLY used when method is 'list_workflow_jobs'
`workflow_runs_filter`	object	—	Filters for workflow runs. ONLY used when method is 'list_workflow_runs'

Parameters from the server's own tool schema.

RISK

Why actions_list is rated Low

This tool performs purely informational operations to retrieve and query GitHub Actions data. It does not create, modify, delete, execute any code, or transfer funds. The blast radius of misuse is minimal—an AI agent could at worst enumerate actions history, which presents no destructive or operational risk.

From the tool's definition Tool description explicitly states 'listing GitHub Actions resources' and lists operations that only 'list workflows', 'list workflow runs', 'list jobs', and 'list artifacts' — all read-only queries with no side effects.

Risk signalsHigh parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs actions_list 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 actions_list, this is the rule to start with:

actions_list Allowed

actions_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "actions_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every actions_list call is checked against it from then on.

FAQ

Questions about actions_list

What does the actions_list tool do? +

Tools for listing GitHub Actions resources. Use this tool to list workflows in a repository, or list workflow runs, jobs, and artifacts for a specific workflow or workflow run. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

What parameters does actions_list accept? +

actions_list accepts 8 parameters: page, repo, owner, method, per_page, resource_id, workflow_jobs_filter, workflow_runs_filter. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on actions_list? +

Register the GitHub MCP server in PolicyLayer and add a rule for actions_list: 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.

What risk level is actions_list? +

actions_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit actions_list? +

Yes. Add a rate_limit block to the actions_list 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.

How do I block actions_list completely? +

Set action: deny in the PolicyLayer policy for actions_list. 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.

What MCP server provides actions_list? +

actions_list is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →