Skip to main content
Glama

UAI x402 Security Tools

github-actions-secret-exposure-scan

Scan GitHub Actions workflow YAML for pull_request_target misuse, over-permissive tokens, secret leakage, unpinned actions, and unsafe fork checkout patterns. (REST equivalent: POST /api/v1/github-actions-secret-exposure-scan, $0.05)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflowYaml": "<workflowYaml>"
    },
    "name": "github-actions-secret-exposure-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowYamlYesGitHub Actions workflow YAML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears most of the burden. It does add real behavioral context by disclosing the pricing ($0.05) and REST equivalent, and 'Scan' plus an input of YAML implies a non-mutating analysis, but it never says what a result looks like (findings list, severity, pass/fail) or whether the YAML is stored.

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?

A single front-loaded sentence that lists the checks without filler, followed by a short parenthetical for cost and the REST route. Nothing is redundant; the parenthetical is a mild addendum rather than core guidance.

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

Completeness3/5

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

For a one-parameter, non-destructive scanning tool with full schema coverage this is close to adequate, but with no output schema and only a title in annotations, the description should still sketch the return shape and any limits. It stops short of that, leaving the agent unsure what comes back.

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

Parameters3/5

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

One parameter at 100% schema description coverage, so the schema already defines 'workflowYaml'. The description adds indirect meaning by telling the agent which constructs are examined, but gives no format detail such as whole-file vs. job snippet, multi-document handling, or size limits.

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

Purpose4/5

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

States a specific verb ('Scan') and a precise resource ('GitHub Actions workflow YAML'), then enumerates five distinct vulnerability classes: pull_request_target misuse, over-permissive tokens, secret leakage, unpinned actions, unsafe fork checkout. That enumeration makes it hard to confuse with generic siblings like secret-scan or dependency-cve-scan, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it holds a workflow YAML file. There is no explicit when-to-use/when-not guidance, no mention of when to prefer the broader secret-scan or repo-security-bundle, and no prerequisites stated.

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