Interleaved cross-org release feed for a collection — same shape as get_latest_releases but scoped to the collection's member orgs. Cursor-paginated: pass limit for slice size (default 20), cursor to continue from a prior call. The result's _meta.pagination carries kind: 'cursor', hasMore, and ne...
Part of the Releases server.
Free to start. No card required.
AI agents call get_collection_releases to retrieve information from Releases without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_collection_releases only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_collection_releases": {}
}
}See the full Releases policy for all 11 tools.
These attack patterns abuse exactly the kind of access get_collection_releases gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Interleaved cross-org release feed for a collection — same shape as get_latest_releases but scoped to the collection's member orgs. Cursor-paginated: pass limit for slice size (default 20), cursor to continue from a prior call. The result's _meta.pagination carries kind: 'cursor', hasMore, and nextCursor when more rows exist; the response text echoes nextCursor so an LLM caller can chain without parsing _meta. Cursors are stable under inserts.. It is categorised as a Read tool in the Releases MCP Server, which means it retrieves data without modifying state.
Register the Releases MCP server in PolicyLayer and add a rule for get_collection_releases: 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_collection_releases 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_collection_releases 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_collection_releases. 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_collection_releases 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.
Deterministic rules across all 11 Releases tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.