Follow an organization or a product so it appears in your personalized feed (get_personalized_feed). Following an organization implicitly includes all of its products. Requires a signed-in user (a relu_ user key or an OAuth token). entity is a typed id — an org_… id or a prod_… id — as returned b...
AI agents use follow to create or update resources in Releases — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Releases environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
entity | string | Yes | Entity to follow — an `org_…` or `prod_…` id (from search / get_* results). |
Parameters from the server's own tool schema.
This tool creates a follow relationship between the user and an organization or product, which is a reversible write operation. It modifies user preferences/feed state but has no destructive, financial, or execution implications. The blast radius is very low — misuse at worst clutters the user's personalized feed with unwanted follows, which can be undone.
From the tool's definition Follow an organization or a product so it appears in your personalized feed. Idempotent: following something you already follow is a no-op.
Attacks that exploit this kind of access
Follow an organization or a product so it appears in your personalized feed (get_personalized_feed). Following an organization implicitly includes all of its products. Requires a signed-in user (a relu_ user key or an OAuth token). entity is a typed id — an org_… id or a prod_… id — as returned by search, get_organization, or get_catalog_entry. Idempotent: following something you already follow is a no-op. It is categorised as a Write tool in the Releases MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
follow accepts 1 parameter: entity. Required: entity. The full parameter table on this page comes from the server's own tool schema.
Register the Releases MCP server in PolicyLayer and add a rule for follow: 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 Releases. Nothing to install.
follow 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 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. 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 is provided by the Releases MCP server (https://mcp.releases.sh/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 →