get_logs

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/get-logs.md

WHAT IT DOES

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

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

Retrieving logs is a read operation with no side effects. Log access may reveal sensitive information (lowering severity from 'very low' to 'low' due to potential information disclosure), but the tool itself does not execute code, modify data, delete data, or move money. The empty description reduces confidence slightly, but the name 'get_logs' strongly indicates a read operation.

From the tool's definition Tool name 'get_logs' indicates retrieval of log data. No description provided, but the name and server context (Supabase management with monitoring capabilities) suggest this fetches existing logs without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_logs Allowed

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

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

FAQ

Questions about get_logs

What does the get_logs tool do? +

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

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

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

Can I rate-limit get_logs? +

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

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

get_logs 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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