check_health

A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted

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/abdqum-supabase-mcp-selfhosted/check-health.md

WHAT IT DOES

What check_health does on Supabase MCP Server - Self-Hosted Edition

AI agents call check_health to retrieve information from Supabase MCP Server - Self-Hosted Edition 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_health is rated Low

Health checks are informational reads that query the status or availability of a system/database without modifying or executing operations. The empty description reduces confidence slightly, but the semantic meaning of 'check_health' is unambiguous—it retrieves system state information. This falls squarely into the Read category with low severity due to minimal blast radius if misused (only information disclosure).

From the tool's definition Tool name 'check_health' indicates a health/status check operation, which is a non-destructive query operation typical of monitoring and diagnostic functions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_health safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_health, this is the rule to start with:

check_health Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every check_health call is checked against it from then on.

FAQ

Questions about check_health

What does the check_health tool do? +

check_health is a read tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Read tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_health? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for check_health: 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 Supabase MCP Server - Self-Hosted Edition. Nothing to install.

What risk level is check_health? +

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

Can I rate-limit check_health? +

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

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

check_health is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.

This server

All 57 Supabase MCP Server - Self-Hosted Edition tools →

Across the catalogue

The MCP Attack Database →

Guides

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