Get release/version history for a deployed app. Use this to see what versions have been deployed, when they were created, and their status.
AI agents call app_releases to retrieve information from Manifest MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical metadata about application releases without creating, modifying, deleting, or executing any operations. It is a pure query/fetch operation with no side effects, fitting the Read category definition.
From the tool's definition Tool description states 'Get release/version history for a deployed app' and lists what can be viewed: 'what versions have been deployed, when they were created, and their status.' These are all read-only retrieval operations with no modification or deletion…
Attacks that exploit this kind of access
Get release/version history for a deployed app. Use this to see what versions have been deployed, when they were created, and their status. It is categorised as a Read tool in the Manifest MCP MCP Server, which means it retrieves data without modifying state.
Register the Manifest MCP server in PolicyLayer and add a rule for app_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 Manifest MCP. Nothing to install.
app_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 app_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 app_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.
app_releases is provided by the Manifest MCP server (manifest-network/manifest-mcp-mono). 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 →