get_advisors
Gets a list of advisory notices for the Supabase project. Use this to check for security vulnerabilities or performance improvements. Include the remediation URL as a clickable link so that the user can reference the issue themselves. It's recommended to run this tool regularly, especially after ...
This record as markdown: /tools/supabase/get-advisors.md
What get_advisors does on Supabase
AI agents call get_advisors 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 |
|---|---|---|---|
type | string | — | The type of advisors to fetch |
project_id | string | — |
Parameters from the server's own tool schema.
Why get_advisors is rated Low
This tool retrieves and queries advisory information from Supabase without modifying, executing, or destructing any data. It is a read-only operation that helps users understand their project's security and performance status. The low severity reflects that misuse would only result in information disclosure, not system compromise or data loss.
From the tool's definition The tool description states it 'Gets a list of advisory notices' and is used to 'check for security vulnerabilities or performance improvements.' The action is purely informational retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_advisors 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_advisors, this is the rule to start with:
get_advisors 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_advisors call is checked against it from then on.
Questions about get_advisors
Gets a list of advisory notices for the Supabase project. Use this to check for security vulnerabilities or performance improvements. Include the remediation URL as a clickable link so that the user can reference the issue themselves. It's recommended to run this tool regularly, especially after making DDL changes to the database since it will catch things like missing RLS policies. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_advisors accepts 2 parameters: type, 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_advisors: 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_advisors 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_advisors 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_advisors. 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_advisors 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