List catalog entries — products and standalone sources combined into one list with an entryType: 'product' | 'source' discriminator per row. Orgs that group multiple sources under a product (e.g. Vercel → Next.js, Turborepo) surface those products; orgs with a single source that isn't part of a p...
Part of the Releases server.
Free to start. No card required.
AI agents call list_catalog 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 list_catalog 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": {
"list_catalog": {}
}
}See the full Releases policy for all 11 tools.
These attack patterns abuse exactly the kind of access list_catalog 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.
List catalog entries — products and standalone sources combined into one list with an entryType: 'product' | 'source' discriminator per row. Orgs that group multiple sources under a product (e.g. Vercel → Next.js, Turborepo) surface those products; orgs with a single source that isn't part of a product surface it directly as an entryType: 'source' entry. Either shape is a reasonable thing to pass to search(entity: ...). Paginated: defaults to 50 entries per page. Pass page: 2 for the next slice. The footer surfaces the total when more pages exist.. 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 list_catalog: 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.
list_catalog 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 list_catalog 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 list_catalog. 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.
list_catalog 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.