New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_get_runner_status

Check a runner's health, version, and last contact time.

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about gitlab_get_runner_status

What does the gitlab_get_runner_status tool do? +

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.

How do I enforce a policy on gitlab_get_runner_status? +

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.

What risk level is gitlab_get_runner_status? +

gitlab_get_runner_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gitlab_get_runner_status? +

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.

How do I block gitlab_get_runner_status completely? +

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.

What MCP server provides gitlab_get_runner_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.