arc_install_controller_hybrid · ARC Config MCP Server MCP

WHAT IT DOES

What arc_install_controller_hybrid does on ARC Config MCP Server

AI agents invoke arc_install_controller_hybrid 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 arc_install_controller_hybrid needs a policy

This tool executes a Helm installation of the GitHub Actions Runner Controller into a Kubernetes cluster. While it also generates configuration files (Write), the dominant and most severe action is executing an external Helm deployment that provisions infrastructure components. Misuse could install malicious or misconfigured controllers affecting all GitHub Actions runners in the cluster, making severity high.

From the tool's definition 'Install GitHub Actions Runner Controller' and 'installs via Helm' — triggers external Helm installation operations in a Kubernetes cluster

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arc_install_controller_hybrid Rate-limited

arc_install_controller_hybrid 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": {
    "arc_install_controller_hybrid": {
      "limits": [
        {
          "counter": "arc_install_controller_hybrid_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 arc_install_controller_hybrid

What does the arc_install_controller_hybrid tool do? +

Install GitHub Actions Runner Controller with configuration versioning. Generates controller config in your repo, allows review, then installs via Helm. 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 arc_install_controller_hybrid? +

Register the ARC Config MCP Server MCP server in PolicyLayer and add a rule for arc_install_controller_hybrid: 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 arc_install_controller_hybrid? +

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

Can I rate-limit arc_install_controller_hybrid? +

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

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

arc_install_controller_hybrid 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.