Documentation for configuring and running a GitHub Actions self-hosted runner. The GitHub Actions runner is pre-installed at /opt/actions-runner. To use it: 1. Get a registration token from GitHub (Settings > Actions > Runners > New self-hosted runner) 2. Configure the runner with --ephemeral fla...
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (token) · Admin/system-level operation
Part of the Autodock server.
Free to start. No card required.
AI agents invoke env.gh_runner to trigger processes or run actions in Autodock. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
env.gh_runner can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"env.gh_runner": {
"limits": [
{
"counter": "env.gh_runner_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Autodock policy for all 27 tools.
These attack patterns abuse exactly the kind of access env.gh_runner gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Documentation for configuring and running a GitHub Actions self-hosted runner. The GitHub Actions runner is pre-installed at /opt/actions-runner. To use it: 1. Get a registration token from GitHub (Settings > Actions > Runners > New self-hosted runner) 2. Configure the runner with --ephemeral flag (auto-unregisters after one job) 3. Start the runner in the background Labels are auto-applied: autodock,<environment-slug> plus any extra labels you specify. IMPORTANT: Runner runs as root and is ephemeral - it processes one job then exits. For continuous runner usage, re-run the configuration and start commands.. It is categorised as a Execute tool in the Autodock MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Autodock MCP server in PolicyLayer and add a rule for env.gh_runner: 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 Autodock. Nothing to install.
env.gh_runner 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 env.gh_runner 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 env.gh_runner. 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.
env.gh_runner is provided by the Autodock MCP server (mikesol/autodock). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Autodock tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.