Check Supabase health status
AI agents call supabase.health to retrieve information from MCP Fullstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive health check query against Supabase infrastructure. It retrieves status data with no side effects, data modification, code execution, or destructive capabilities. The low severity reflects minimal blast radius—misuse would only return status information that is typically publicly available or non-sensitive system metrics.
From the tool's definition Tool name 'supabase.health' and description 'Check Supabase health status' indicate a read-only query operation that retrieves system status information without modifying or executing anything.
Attacks that exploit this kind of access
Check Supabase health status. It is categorised as a Read tool in the MCP Fullstack MCP Server, which means it retrieves data without modifying state.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for supabase.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 MCP Fullstack. Nothing to install.
supabase.health is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the supabase.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.
Set action: deny in the PolicyLayer policy for supabase.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.
supabase.health is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →