manage_webhooks
A write tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/manage-webhooks.md
What manage_webhooks does on Supabase MCP Server - Self-Hosted Edition
AI agents use manage_webhooks to create or update resources in Supabase MCP Server - Self-Hosted Edition, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server - Self-Hosted Edition environment.
Why manage_webhooks is rated Medium
Webhook management typically enables creation or modification of event handlers and external integrations, which constitutes reversible Write operations. However, without explicit description details, confidence is moderate.
From the tool's definition Tool name 'manage_webhooks' with empty description; context shows it operates within Supabase's webhook infrastructure for event-driven operations. Webhook management involves creating, updating, or modifying webhook configurations and endpoints.
Attacks that exploit this kind of access
The rule that runs manage_webhooks 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 manage_webhooks, this is the rule to start with:
manage_webhooks stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every manage_webhooks call is checked against it from then on.
Questions about manage_webhooks
manage_webhooks is a write tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Write tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for manage_webhooks: 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.
manage_webhooks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_webhooks 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 manage_webhooks. 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.
manage_webhooks 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.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
Across the catalogue