Create a webhook subscription. The response includes webhook_secret ONCE; the bot must persist it for HMAC validation. Counts against the subscription cap.
AI agents use create_webhook to create or update resources in Feedbagel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Feedbagel MCP Server environment.
This tool creates a new webhook subscription, which is a reversible write operation that persists new data in the user's account. It modifies the user's webhook configuration but does not delete data or execute arbitrary code.
From the tool's definition Tool description explicitly states 'Create a webhook subscription' and 'Counts against the subscription cap', indicating creation of a new resource that modifies the user's webhook configuration state.
Attacks that exploit this kind of access
Create a webhook subscription. The response includes webhook_secret ONCE; the bot must persist it for HMAC validation. Counts against the subscription cap. It is categorised as a Write tool in the Feedbagel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Feedbagel MCP Server MCP server in PolicyLayer and add a rule for create_webhook: 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.
create_webhook 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 create_webhook 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 create_webhook. 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.
create_webhook 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 →