Resume deliveries for a paused webhook subscription.
AI agents use resume_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.
The tool modifies the state of a webhook subscription by resuming paused deliveries. This is a Write operation because it changes system configuration reversibly. Severity is medium because resuming webhook deliveries could trigger unintended notifications or downstream actions if an agent mistakenly resumes the wrong webhook, but the action is reversible (can be paused again).
From the tool's definition Tool name 'resume_webhook' and description 'Resume deliveries for a paused webhook subscription' indicate modification of webhook state.
Attacks that exploit this kind of access
Resume deliveries for a paused webhook subscription. 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 resume_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.
resume_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 resume_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 resume_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.
resume_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 →