detach_feed_from_webhook · Feedbagel MCP Server MCP

WHAT IT DOES

What detach_feed_from_webhook does on Feedbagel MCP Server

AI agents use detach_feed_from_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.

WHY IT NEEDS A POLICY

Why detach_feed_from_webhook needs a policy

Detaching a feed from a webhook modifies the webhook subscription configuration by removing a feed association. This is a reversible write operation since the feed can be re-attached. It is not destructive (no data is deleted), not financial, and not execute. Severity is medium because misuse could silently stop feed delivery, causing missed updates for users.

From the tool's definition 'Stop delivering a feed' — detaching a feed from a webhook removes an association but is likely reversible by re-attaching via 'attach_feed_to_webhook'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detach_feed_from_webhook Rate-limited

detach_feed_from_webhook 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "detach_feed_from_webhook": {
      "limits": [
        {
          "counter": "detach_feed_from_webhook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Feedbagel MCP Server, so you can run agents against it safely.

FAQ

Questions about detach_feed_from_webhook

What does the detach_feed_from_webhook tool do? +

Stop delivering a feed. 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.

How do I enforce a policy on detach_feed_from_webhook? +

Register the Feedbagel MCP Server MCP server in PolicyLayer and add a rule for detach_feed_from_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.

What risk level is detach_feed_from_webhook? +

detach_feed_from_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit detach_feed_from_webhook? +

Yes. Add a rate_limit block to the detach_feed_from_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.

How do I block detach_feed_from_webhook completely? +

Set action: deny in the PolicyLayer policy for detach_feed_from_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.

What MCP server provides detach_feed_from_webhook? +

detach_feed_from_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.