deploy_github_runners · ARC Config MCP Server MCP

WHAT IT DOES

What deploy_github_runners does on ARC Config MCP Server

AI agents invoke deploy_github_runners to trigger actions in ARC Config MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why deploy_github_runners needs a policy

This tool executes infrastructure deployment operations in a Kubernetes cluster. While not immediately destructive or financial, deploying GitHub Actions runners with configurable scaling can consume significant cloud resources, create new workloads, and affect CI/CD pipelines. Misuse could spawn unintended runner replicas, consuming resources or creating security perimeters.

From the tool's definition Tool 'deploy_github_runners' deploys runners with 'configurable auto-scaling' and 'replica counts', triggering external Kubernetes operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_github_runners Rate-limited

deploy_github_runners stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_github_runners": {
      "limits": [
        {
          "counter": "deploy_github_runners_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about deploy_github_runners

What does the deploy_github_runners tool do? +

Deploy GitHub Actions runners with configurable auto-scaling. Supports setting minimum and maximum replica counts for optimal resource management. It is categorised as a Execute tool in the ARC Config MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_github_runners? +

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

What risk level is deploy_github_runners? +

deploy_github_runners is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_github_runners? +

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

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

deploy_github_runners is provided by the ARC Config MCP Server MCP server (tsviz/arc-config-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.