Run any gh (GitHub CLI) subcommand. Pass the args as a list (no leading gh). Pre-flights install + auth state, returns a clear error when the CLI is missing or unauthed. Use this for anything not covered by the specific github_* tools (e.g. gh repo create, gh release create, gh secret set).
AI agents invoke gh_run to trigger actions in Yaver. 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 |
|---|---|---|---|
args | array | Yes | subcommand + flags, e.g. ["repo", "view", "--json", "description"] |
directory | string | — | Working directory; defaults to agent cwd |
Parameters from the server's own tool schema.
gh_run triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
Run any gh (GitHub CLI) subcommand. Pass the args as a list (no leading gh). Pre-flights install + auth state, returns a clear error when the CLI is missing or unauthed. Use this for anything not covered by the specific github_* tools (e.g. gh repo create, gh release create, gh secret set). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gh_run accepts 2 parameters: args, directory. Required: args. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for gh_run: 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 Yaver. Nothing to install.
gh_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gh_run 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 gh_run. 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.
gh_run is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.