Scale GitHub Actions runners with intelligent cost and performance recommendations.
AI agents invoke arc_scale_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.
Scaling runners in a Kubernetes cluster is an Execute action—it triggers infrastructure changes whose effects depend on the scaling arguments provided (number of runners, resource allocation, etc.).
From the tool's definition Tool performs 'Scale GitHub Actions runners' which executes infrastructure scaling operations in Kubernetes clusters.
Attacks that exploit this kind of access
Scale GitHub Actions runners with intelligent cost and performance recommendations. 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.
Register the ARC Config MCP Server MCP server in PolicyLayer and add a rule for arc_scale_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.
arc_scale_runners is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the arc_scale_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.
Set action: deny in the PolicyLayer policy for arc_scale_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.
arc_scale_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →