github_action

Interact with the GitHub REST API: search/read repos, create branches and commits, open PRs, comment, merge, and read workflow checks.

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/github-action.md

WHAT IT DOES

What github_action does on UnClick

AI agents invoke github_action to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`ref`	string	—	Commit SHA, branch, or tag for list_checks.
`base`	string	—	Pull request base branch.
`body`	string	—	Issue, pull request, or comment body text.
`head`	string	—	Pull request head branch.
`page`	number	—	Page number.
`repo`	string	—	Repository name.
`draft`	boolean	—	Create a draft pull request.
`files`	array	—	Files for push_files: { path, content, encoding? } entries.
`force`	boolean	—	Force-update the branch ref during push_files. Defaults to false.
`owner`	string	—	Repository owner login.
`query`	string	—	Search query string (for search_repos and search_code).
`state`	string	—	Filter by state: open, closed, all.

Parameters from the server's own tool schema.

RISK

Why github_action is rated High

This tool spans multiple categories. It can read repos and workflow checks (Read), but also creates branches, commits, and opens PRs (Write), and can merge PRs (Execute/potentially Destructive). Merging PRs is an irreversible action that can alter the state of a codebase permanently.

From the tool's definition create branches and commits, open PRs, comment, merge, and read workflow checks

Risk signalsAccepts file system path (files[].path) · Handles credentials or secrets (access_token) · Accepts raw HTML/template content (body) · High parameter count (38 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_action safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_action, this is the rule to start with:

github_action Rate-limited

github_action stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_action": {
      "limits": [
        {
          "counter": "github_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_action

What does the github_action tool do? +

Interact with the GitHub REST API: search/read repos, create branches and commits, open PRs, comment, merge, and read workflow checks. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does github_action accept? +

github_action accepts 12 parameters: ref, base, body, head, page, repo, draft, files, force, owner, query, state. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on github_action? +

Register the UnClick MCP server in PolicyLayer and add a rule for github_action: 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 UnClick. Nothing to install.

What risk level is github_action? +

github_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit github_action? +

Yes. Add a rate_limit block to the github_action 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 github_action completely? +

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

github_action is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →