AI agents use github_action to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | Issue body text (for create_issue). |
page | number | — | Page number. |
repo | string | — | Repository name. |
owner | string | — | Repository owner login. |
query | string | — | Search query string (for search_repos and search_code). |
state | string | — | Filter by state: open, closed, all. |
title | string | — | Issue title (for create_issue). |
action | string | Yes | Action: search_repos, get_repo, list_issues, create_issue, list_prs, get_user, list_gists, search_code. |
labels | string | — | Comma-separated label names to filter by. |
per_page | number | — | Results per page (max 100). |
username | string | — | GitHub username (for get_user and list_gists). |
access_token | string | — | GitHub personal access token (PAT). Public data works without a token. |
Parameters from the server's own tool schema.
The tool can both read and write GitHub data. 'Create issues' is a write operation that modifies GitHub repositories by adding new issues. While many operations are read-only (search repos, get repo details, list PRs, get user profiles, list gists, search code), the ability to create issues means the most severe applicable category is Write.
From the tool's definition list and create issues
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (access_token) · Accepts raw HTML/template content (body) · High parameter count (12 properties)
Attacks that exploit this kind of access
Interact with the GitHub REST API: search repos, get repo details, list and create issues, list PRs, get user profiles, list gists, and search code. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
github_action accepts 12 parameters: body, page, repo, owner, query, state, title, action, labels, per_page, username, access_token. Required: action. The full parameter table on this page comes from the server's own tool schema.
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.
github_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
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 →