ci_create_binding · Run402 MCP: Risk & Policy

WHAT IT DOES

What ci_create_binding does on Run402

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

WHY IT NEEDS A POLICY

Why ci_create_binding needs a policy

This tool creates a new binding that grants CI/CD deployment authority to a GitHub repository/branch. While it does not itself sign or broaden authority, it establishes a persistent authorization relationship that allows CI pipelines to deploy infrastructure.

From the tool's definition Create a GitHub Actions CI/OIDC deploy binding by sending a locally signed delegation to the SDK

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ci_create_binding Rate-limited

ci_create_binding 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": {
    "ci_create_binding": {
      "limits": [
        {
          "counter": "ci_create_binding_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Run402, so you can run agents against it safely.

FAQ

Questions about ci_create_binding

What does the ci_create_binding tool do? +

Create a GitHub Actions CI/OIDC deploy binding by sending a locally signed delegation to the SDK. This MCP wrapper does not sign or broaden authority; the signed delegation defines the repository/branch or environment, allowed events/actions, and optional route_scopes. Without route_scopes, CI cannot deploy route declarations. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ci_create_binding? +

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

What risk level is ci_create_binding? +

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

Can I rate-limit ci_create_binding? +

Yes. Add a rate_limit block to the ci_create_binding 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 ci_create_binding completely? +

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

ci_create_binding is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.