Your personalized release feed — recent releases from the organizations and products you follow, newest first. Requires a signed-in user. Same item shape as get_latest_releases, scoped to your follows. Cursor-paginated: pass cursor from a prior response's _meta.pagination.nextCursor and optional ...
AI agents call get_personalized_feed to retrieve information from Releases without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Entries per page (1–100). Defaults to 30. |
cursor | string | — | Opaque cursor from a previous page's `_meta.pagination.nextCursor`. |
Parameters from the server's own tool schema.
This tool purely retrieves and queries data (releases) filtered by user preferences. It has no side effects—it neither creates, modifies, deletes, nor executes operations. The pagination mechanism and optional limit parameter are standard Read-category patterns for data retrieval. Misuse would at worst expose information the user is already authorized to see, presenting minimal security risk.
From the tool's definition Tool retrieves 'your personalized release feed' of 'recent releases' scoped to followed items. Operations are queries returning data with no modification: 'cursor-paginated' retrieval with optional limit parameter.
Attacks that exploit this kind of access
Your personalized release feed — recent releases from the organizations and products you follow, newest first. Requires a signed-in user. Same item shape as get_latest_releases, scoped to your follows. Cursor-paginated: pass cursor from a prior response's _meta.pagination.nextCursor and optional limit (1–100, default 30). It is categorised as a Read tool in the Releases MCP Server, which means it retrieves data without modifying state.
get_personalized_feed accepts 2 parameters: limit, cursor. 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 get_personalized_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 Releases. Nothing to install.
get_personalized_feed is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_personalized_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 get_personalized_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.
get_personalized_feed 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 →