This record as markdown: /tools/io-github-kivanccakmak-yaver/supabase-functions.md
What supabase_functions does on Yaver
AI agents call supabase_functions to retrieve information from Yaver 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why supabase_functions is rated Low
This tool performs a read-only operation to list/query Supabase Edge Functions. It retrieves data without side effects, making it a Read category tool. The severity is low because listing functions does not expose sensitive functionality or create risk of significant harm—it is purely informational. Confidence is high due to the clear, explicit 'List' verb in the description.
From the tool's definition The tool is described as 'List Supabase Edge Functions', which is a retrieval operation that queries and returns information about existing functions without modifying or executing them.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs supabase_functions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_functions, this is the rule to start with:
supabase_functions 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 Yaver, apply this rule, and every supabase_functions call is checked against it from then on.
Questions about supabase_functions
List Supabase Edge Functions. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
supabase_functions accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for supabase_functions: 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 Yaver. Nothing to install.
supabase_functions 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_functions 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_functions. 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_functions is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue