Skip to main content
Glama

Ravi CI Guard: GitHub Actions security audit

Pin actions to commit SHAs

pin_actions
Read-only

Resolve uses: references to immutable commit SHAs live from GitHub: actions=actions/checkout@v4,docker/login-action@v3 (up to 20), or repo=/url=/yaml= to pin every uses: in those workflows. Per action: SHA (annotated tags peeled), the exact version tag for the "# v4.2.2" comment, a ready uses: line, latest release and whether a newer major exists. Needs a CI Guard pass (0.50 USDC = 24 h, 3 USDC = 30 days + Team Kit, 8 USDC = 90 days + Team Kit, by plain USDC transfer on Base; see payment_options), or pay per call over HTTP x402 ($0.02) at /v1/gha/pin.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pin_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOptional branch, tag or commit SHA for repo= (default: the default branch)
urlNoAlternative: https URL of one workflow file (github.com blob/raw, raw.githubusercontent.com, gist)
passNoOptional CI Guard pass token (rcg1...). Better: set it once as the MCP header Authorization: Bearer <token>.
repoNoAlternative to actions: pin every uses: in this public repo's workflows (owner/name)
yamlNoAlternative: the workflow file text itself (POST JSON {"yaml": "..."} recommended; up to 64 KB)
actionsNoComma-separated owner/repo[/path]@ref list, e.g. actions/checkout@v4,actions/setup-node@v4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial unstated behavior: the 20-action cap, that annotated tags are peeled to SHAs, the per-action payload (SHA, version tag for the '# v4.2.2' comment, ready uses: line, latest release, newer-major flag), and the auth/payment model (CI Guard pass durations or $0.02 per-call x402). That is real operational context an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and modes are front-loaded, then behavior, then payment. The three-tier USDC pricing clause is bulky detail that is already delegated to payment_options, so it costs some density, but nothing is genuinely misleading or wasted filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the per-action return shape, and it covers inputs, limits, authentication, and payment. An agent has everything needed to invoke it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the 'up to 20' limit on actions= and clarifies that repo=/url=/yaml= pin every uses: in the target workflow, which the schema's 'Alternative' labels only imply. It does not add syntax help for ref= or pass= beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Resolve uses: references to immutable commit SHAs') and enumerates the three input modes (actions=, repo=/url=/yaml=). An agent can distinguish this from audit_workflows or peek_workflows without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for each mode and names the exact batch list format, plus points to payment_options and the HTTP x402 endpoint for payment. It does not explicitly say when to prefer repo=/url=/yaml= over each other or when a sibling tool like audit_workflows is the better call, so the routing guidance is context-rich but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources