restricted-tool-triage

Triage tool-denial events in gh-aw workflows with restricted tool allowlists.

5.1k|530|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill restricted-tool-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: restricted-tool-triage
Source: https://github.com/github/gh-aw/tree/main/.github/skills/restricted-tool-triage
Command: npx skills add https://github.com/github/gh-aw --skill restricted-tool-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents running inside gh-aw workflows with narrow tools: allowlists can burn through a hard, non-renewable denial budget (commonly 3 denied tool calls) by retrying disallowed commands, causing the harness to abort the entire session with guard.tool_denials_exceeded.

Core Features & Use Cases

  • Allowlist-first execution: Read the workflow's declared tools: block (bash list, MCP toolsets, edit permissions) before issuing any shell, file, or MCP command.
  • Denial triage procedure: On the first denial, pivot to an allowed capability substitute instead of retrying variants of the same disallowed command.
  • Accurate gap reporting: Avoid misreporting intentional least-privilege restrictions as credential or permission bugs, and cite the exact denied commands when reporting a genuine missing capability.
  • Use Case: An agent in a gh-aw workflow with a short bash: allowlist gets "permission denied" on git status; instead of probing variants, it switches to an allowed git diff command, completes the task, and notes the constraint.

Quick Start

When a tool call is denied inside a gh-aw workflow, apply this skill to check the declared tools allowlist, switch to an allowed capability, and finish the task without exhausting the denial budget.

Frequently Asked Questions about restricted-tool-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle permission denied tool errors in a gh-aw workflow?

Stop retrying variants of the denied command and instead identify the capability you need, then map it to a tool explicitly present in the workflow's declared tools allowlist. Each denial spends a non-renewable budget that aborts the session when exhausted.

What is the tool denial budget in gh-aw agentic workflows?

gh-aw enforces a hard, non-renewable denial budget per session, commonly 3 denied tool calls. Once the threshold is reached, the harness emits guard.tool_denials_exceeded and aborts the entire session immediately with no recovery.

Why does my gh-aw workflow deny shell commands like git status?

The workflow frontmatter declares a narrow tools allowlist, such as a short bash list or scoped MCP toolsets, which intentionally restricts available commands. This is usually a deliberate least-privilege security design, not a misconfiguration or credential problem.

Should I report missing tools as a permissions or credentials bug?

No. A tools allowlist denial is an intentional restriction, not an auth or token scope issue. If you report a gap, name the specific missing capability and cite the exact denied commands instead of suggesting maintainers loosen permissions.

What should an agent do when a required capability has no allowed substitute?

Stop probing disallowed tools, complete whatever parts of the task are possible with allowed tools, and clearly note the limitation in the final output. Continuing to probe risks exhausting the denial budget and terminating the session.