health_check

Verify the local gateway is alive and reachable from ChatGPT.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/health-check.md

WHAT IT DOES

What health_check does on LocalAnt

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

RISK

Why health_check is rated Low

This is a diagnostic/monitoring tool that queries the state of the gateway without modifying, executing, or deleting anything. It retrieves reachability status information, fitting the Read category. Severity is low because even if misused, it only performs a harmless connectivity check with no blast radius.

From the tool's definition Tool name 'health_check' and description 'Verify the local gateway is alive and reachable' indicates a simple status probe with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs health_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, 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:

health_check Allowed

health_check 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": {
    "health_check": {}
  }
}

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

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

FAQ

Questions about health_check

What does the health_check tool do? +

Verify the local gateway is alive and reachable from ChatGPT. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health_check? +

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

What risk level is health_check? +

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

Can I rate-limit health_check? +

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

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

health_check is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

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