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.

SERVERMcp SOURCE@clarxai/mcp

Medium RISK CLASS

Category Write

Parameters 60 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/ai-clarx-mcp/get-ci-workflow.md

WHAT IT DOES

What get_ci_workflow does on Mcp

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.

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

Parameters from the server's own tool schema.

RISK

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 definition Write the result to .github/workflows/clarx.yml

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_ci_workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ci_workflow, this is the rule to start with:

get_ci_workflow Rate-limited

get_ci_workflow stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_ci_workflow call is checked against it from then on.

FAQ

Questions about get_ci_workflow

What does the get_ci_workflow tool do? +

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. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does get_ci_workflow accept? +

get_ci_workflow accepts 6 parameters: min_score, cli_version, upload_sarif, ignore_patterns, upload_artifact, min_pillar_score. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_ci_workflow? +

Register the MCP server in PolicyLayer and add a rule for get_ci_workflow: 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 Mcp. Nothing to install.

What risk level is get_ci_workflow? +

get_ci_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit get_ci_workflow? +

Yes. Add a rate_limit block to the get_ci_workflow 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.

How do I block get_ci_workflow completely? +

Set action: deny in the PolicyLayer policy for get_ci_workflow. 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.

What MCP server provides get_ci_workflow? +

get_ci_workflow is provided by the MCP server (@clarxai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 5 tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →