Pause deliveries for a webhook subscription. Existing attachments stay; the poller skips this subscriber until resumed.
AI agents use pause_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.
Pausing a webhook modifies its state (active → paused) but is reversible — deliveries can be resumed. No data is deleted, no code is executed, and no financial transaction occurs. The blast radius is medium: an agent misusing this tool could disrupt event delivery for a subscription, causing missed feed updates until manually resumed.
From the tool's definition 'Pause deliveries for a webhook subscription' and 'the poller skips this subscriber until resumed'
Attacks that exploit this kind of access
Pause deliveries for a webhook subscription. Existing attachments stay; the poller skips this subscriber until resumed. 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 pause_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.
pause_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 pause_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 pause_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.
pause_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 →