Deploy GitHub Actions runners with configuration versioning. Generates config files in your repo, allows review, then optionally applies to cluster.
AI agents invoke arc_deploy_runners_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.
This tool executes commands against Kubernetes clusters to deploy GitHub Actions runners. While it includes a review step (mitigating factor), it ultimately triggers irreversible operational changes in a live environment. This falls under Execute rather than Write because the effects are infrastructure-level deployments whose consequences depend on cluster state and configuration.
From the tool's definition Tool performs 'Deploy GitHub Actions runners' and 'applies to cluster' which are operational changes to Kubernetes infrastructure. Description states it 'applies to cluster' — a direct execution of infrastructure changes with external effects.
Attacks that exploit this kind of access
Deploy GitHub Actions runners with configuration versioning. Generates config files in your repo, allows review, then optionally applies to cluster. 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_deploy_runners_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.
arc_deploy_runners_hybrid 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_deploy_runners_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.
Set action: deny in the PolicyLayer policy for arc_deploy_runners_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.
arc_deploy_runners_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.
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 →