gitlab_get_runner_status
Check a runner's health, version, and last contact time.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-get-runner-status.md
What gitlab_get_runner_status does on Gitlab
AI agents call gitlab_get_runner_status to retrieve information from Gitlab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gitlab_get_runner_status is rated Low
This tool retrieves operational metadata about a GitLab runner (health status, version, contact time). It performs a read-only query with no capability to modify infrastructure, execute workloads, delete resources, or trigger financial transactions. The blast radius of misuse is minimal—an agent could only gather information about runner availability, not alter deployments or cause infrastructure damage.
From the tool's definition Tool name and description indicate a status check operation: 'Check a runner's health, version, and last contact time.' These are query/retrieve operations with no side effects, mutations, or external command execution.
Attacks that exploit this kind of access
The rule that runs gitlab_get_runner_status 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_get_runner_status, this is the rule to start with:
gitlab_get_runner_status is read-only, so it stays allowed. 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_get_runner_status call is checked against it from then on.
Questions about gitlab_get_runner_status
Check a runner's health, version, and last contact time. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_get_runner_status: 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_get_runner_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gitlab_get_runner_status 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_get_runner_status. 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_get_runner_status 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.
This server
Across the catalogue