check_gitness

Check Gitness (Harness git hosting) health via GET /api/v1/health. Returns 200 when service is up. Default port 3000.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-gitness.md

WHAT IT DOES

What check_gitness does on Mcp Nettools

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

RISK

Why check_gitness is rated Low

This is a straightforward health check that retrieves service status information. It is a read-only operation with no side effects, no ability to modify data, and no capability to execute code or trigger external operations. The blast radius of misuse is minimal—an attacker could only learn whether a Gitness service is running, which is low-value reconnaissance. Classified as Read with low severity.

From the tool's definition Tool performs a GET request to a health endpoint (/api/v1/health) that returns service status (200 when up). No data modification, deletion, or execution of arbitrary code is possible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_gitness safely

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

check_gitness Allowed

check_gitness is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_gitness call is checked against it from then on.

FAQ

Questions about check_gitness

What does the check_gitness tool do? +

Check Gitness (Harness git hosting) health via GET /api/v1/health. Returns 200 when service is up. Default port 3000. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_gitness? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_gitness: 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 Mcp Nettools. Nothing to install.

What risk level is check_gitness? +

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

Can I rate-limit check_gitness? +

Yes. Add a rate_limit block to the check_gitness 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 check_gitness completely? +

Set action: deny in the PolicyLayer policy for check_gitness. 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 check_gitness? +

check_gitness is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →