get_logs
Gets logs for a Supabase project by service type. Use this to help debug problems with your app. This will return logs within the last 24 hours.
This record as markdown: /tools/supabase/get-logs.md
What get_logs does on Supabase
AI agents call get_logs to retrieve information from Supabase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
service | string | — | The service to fetch logs for |
project_id | string | — |
Parameters from the server's own tool schema.
Why get_logs is rated Low
This tool only retrieves and queries existing log data without any side effects. It is a pure read operation used for observability and debugging. No data is created, modified, deleted, or executed. The severity is low because log access is typically informational and does not directly impact system state, though logs may contain sensitive information depending on what is logged.
From the tool's definition Tool name is 'get_logs' and description states 'Gets logs for a Supabase project' - retrieval operation with no modification, deletion, or execution capability. Returns historical data (logs within last 24 hours) for debugging purposes.
Attacks that exploit this kind of access
The rule that runs get_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every get_logs call is checked against it from then on.
Questions about get_logs
Gets logs for a Supabase project by service type. Use this to help debug problems with your app. This will return logs within the last 24 hours. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_logs accepts 2 parameters: service, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Supabase 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. Nothing to install.
get_logs 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 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.
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.
get_logs is provided by the Supabase MCP server (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase, and thousands of servers like it.
This server
Across the catalogue