Add a feed to the user
AI agents use follow_feed 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 creates a new subscription or feed association for the user. This is a Write operation because it modifies user data (their feed list) in a reversible manner—the user can later 'detach' or remove the feed. It is not Destructive (can be undone), not Execute (does not run arbitrary code), not Financial (no money involved), and not Read (has side effects).
From the tool's definition Tool description states 'Add a feed to the user', which is a create/modify operation. This is confirmed by the action verb 'follow' (subscribe/add) and the presence of sibling destructive tools like 'delete_webhook' and 'detach_feed_from_webhook' that suggest…
Attacks that exploit this kind of access
Add a feed to the user. 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 follow_feed: 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.
follow_feed 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 follow_feed 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 follow_feed. 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.
follow_feed 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 →