List all webhook subscriptions owned by the user.
AI agents call list_webhooks to retrieve information from Feedbagel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation with no side effects. It queries and returns webhook subscription data for informational purposes only. The user retains full control over the data, and the operation is non-destructive and non-mutative.
From the tool's definition Tool name 'list_webhooks' and description 'List all webhook subscriptions owned by the user' indicate a read-only query operation that retrieves existing webhook configurations without modification or deletion.
Attacks that exploit this kind of access
List all webhook subscriptions owned by the user. It is categorised as a Read tool in the Feedbagel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Feedbagel MCP Server MCP server in PolicyLayer and add a rule for list_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 Feedbagel MCP Server. Nothing to install.
list_webhooks 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 list_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 list_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.
list_webhooks is provided by the Feedbagel MCP Server MCP server (prototypr/feedbagel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →