gitlab_register_local_runner
A execute tool on the Gitlab MCP server.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-register-local-runner.md
What gitlab_register_local_runner does on Gitlab
AI agents invoke gitlab_register_local_runner to trigger actions in Gitlab. 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 gitlab_register_local_runner is rated High
Registering a local runner connects a machine to GitLab to execute CI/CD pipeline jobs, which is an external operation that enables code execution on infrastructure. The description is empty, lowering confidence, but the tool name strongly implies it registers a GitLab CI runner — an agent that executes arbitrary pipeline jobs.
From the tool's definition Tool name 'gitlab_register_local_runner' on a server managing 'runners' in the GitLab DevOps lifecycle
Attacks that exploit this kind of access
The rule that runs gitlab_register_local_runner safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_register_local_runner, this is the rule to start with:
gitlab_register_local_runner 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab, apply this rule, and every gitlab_register_local_runner call is checked against it from then on.
Questions about gitlab_register_local_runner
gitlab_register_local_runner is a execute tool on the Gitlab MCP server. It is categorised as a Execute tool in the Gitlab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_register_local_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 Gitlab. Nothing to install.
gitlab_register_local_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 gitlab_register_local_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 gitlab_register_local_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.
gitlab_register_local_runner is provided by the Gitlab MCP server (dkeeno/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitlab, and thousands of servers like it.
Across the catalogue