metrics_dashboard

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/metrics-dashboard.md

WHAT IT DOES

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

AI agents call metrics_dashboard 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 metrics_dashboard is rated Low

The name 'metrics_dashboard' strongly implies a read-only operation that retrieves and displays performance or operational metrics. Dashboards are typically read-only views of data. However, confidence is low due to the empty description — it's possible this tool has side effects not indicated by the name alone.

From the tool's definition Tool name 'metrics_dashboard' suggests reading/displaying metrics data. Description is empty, providing no additional context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs metrics_dashboard 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 metrics_dashboard, this is the rule to start with:

metrics_dashboard Allowed

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

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 metrics_dashboard call is checked against it from then on.

FAQ

Questions about metrics_dashboard

What does the metrics_dashboard tool do? +

metrics_dashboard 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 metrics_dashboard? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for metrics_dashboard: 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 metrics_dashboard? +

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

Can I rate-limit metrics_dashboard? +

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

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

metrics_dashboard 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 →