# get_ci_workflow

Generate a GitHub Actions workflow YAML that gates pull requests on the Clarx AI-readiness score (npx @clarxai/cli). Write the result to .github/workflows/clarx.yml.

Agent View of the PolicyLayer registry record for `get_ci_workflow`. HTML page: https://policylayer.com/tools/ai-clarx-mcp/get-ci-workflow

## Facts

- Tool: `get_ci_workflow`
- Server: Mcp (`@clarxai/mcp`) — https://policylayer.com/tools/ai-clarx-mcp.md
- Install: `npx -y @clarxai/mcp`
- Homepage: https://github.com/Gernika-Labs/clarx-cloud
- Risk category: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 6
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `min_score` | number | no | Fail the check when the overall score is below this (0-100). |
| `cli_version` | string | no | @clarxai/cli version to pin. |
| `upload_sarif` | boolean | no | Upload findings as SARIF to GitHub code scanning. |
| `ignore_patterns` | array | no | Glob patterns to exclude from scoring, e.g. ['vendor/**']. |
| `upload_artifact` | boolean | no | Attach a markdown report artifact to the run. |
| `min_pillar_score` | number | null | no | Optional per-pillar floor. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

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

## Why get_ci_workflow is rated Medium

This tool generates and writes a GitHub Actions workflow YAML file to the repository at .github/workflows/clarx.yml. This is a file creation/write operation that modifies the repository's CI configuration. While it could influence CI behavior, it is a reversible write (the file can be deleted or overwritten).

From the tool's own definition: "Write the result to .github/workflows/clarx.yml"

## Use case

AI agents use get_ci_workflow to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_ci_workflow": {
      "limits": [
        {
          "counter": "get_ci_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp (4)

- `analyze_clarx_manifest` — Read — https://policylayer.com/tools/ai-clarx-mcp/analyze-clarx-manifest.md
- `analyze_manifest` — Read — https://policylayer.com/tools/ai-clarx-mcp/analyze-manifest.md
- `generate_manifest_draft` — Write — https://policylayer.com/tools/ai-clarx-mcp/generate-manifest-draft.md
- `suggest_manifest_fix` — Write — https://policylayer.com/tools/ai-clarx-mcp/suggest-manifest-fix.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-clarx-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-clarx-mcp