arc_install_controller · ARC Config MCP Server MCP

WHAT IT DOES

What arc_install_controller does on ARC Config MCP Server

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

This tool installs software into a Kubernetes cluster, which is an active deployment operation that triggers external infrastructure changes. It is not merely writing data but executing an installation process with real operational effects on the cluster environment. Misuse could result in unauthorized or misconfigured deployments affecting cluster stability and security.

From the tool's definition Install GitHub Actions Runner Controller in Kubernetes cluster with live status updates in chat

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arc_install_controller Rate-limited

arc_install_controller 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": {
      "limits": [
        {
          "counter": "arc_install_controller_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

What does the arc_install_controller tool do? +

Install GitHub Actions Runner Controller in Kubernetes cluster with live status updates in chat. 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? +

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

arc_install_controller 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? +

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

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

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