health_check

What health_check does on Gitlab Mcp

AI agents call health_check to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why health_check is rated Low

Health checks are inherently read-only operations that query system state without modifying any data, executing code, or triggering external operations. Authentication verification is a standard diagnostic operation. This poses minimal risk even if called by an AI agent, as it cannot alter data or invoke destructive actions.

From the tool's definition Tool description states 'Verify server status and authentication' — this is a diagnostic/status check operation with no data modification or side effects. The verb 'verify' and context of 'health check' indicate a read-only query.

The rule that runs health_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_check, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "health_check": {}
  }
}

Questions about health_check