arc_manage_runners · ARC Config MCP Server MCP

WHAT IT DOES

What arc_manage_runners does on ARC Config MCP Server

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

This tool goes beyond read-only listing; it can scale (modify replica counts of runner deployments in Kubernetes) and manage runners (start, stop, reconfigure), which are stateful external operations. While listing is a read action, the most severe applicable category is Execute because scaling and management operations affect live infrastructure.

From the tool's definition 'scale, and manage GitHub Actions runners with real-time updates' — scaling runners modifies live Kubernetes workloads and triggers external operations whose effects depend on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arc_manage_runners Rate-limited

arc_manage_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": {
    "arc_manage_runners": {
      "limits": [
        {
          "counter": "arc_manage_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 arc_manage_runners

What does the arc_manage_runners tool do? +

List, scale, and manage GitHub Actions runners with real-time updates. 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_manage_runners? +

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

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

Can I rate-limit arc_manage_runners? +

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

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

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