Find releases in an Octopus Deploy space. Three modes, picked by which arguments are supplied: - releaseId → fetch the summary for that release. - projectId → list releases for that project (optionally filtered by searchByVersion). - neither → list releases across the space. Each summary includes...
AI agents call find_releases to retrieve information from Octopus Deploy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries release data from Octopus Deploy without side effects. It supports three read-only modes: fetching a release summary by ID, listing releases for a project, or listing releases across the space. The ability to fetch a full release body via resourceUri is still a read operation. No create, update, delete, or execute operations are mentioned.
From the tool's definition Tool description states it "Find[s] releases" and "list[s] releases". The server description emphasizes "read-only access" and "inspect, query, and diagnose". No modification, creation, deletion, or execution capabilities are mentioned.
Documented attack patterns abuse exactly the kind of access find_releases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octopus Deploy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_releases:
{
"version": "1",
"default": "deny",
"tools": {
"find_releases": {}
}
}find_releases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find releases in an Octopus Deploy space. Three modes, picked by which arguments are supplied: - releaseId → fetch the summary for that release. - projectId → list releases for that project (optionally filtered by searchByVersion). - neither → list releases across the space. Each summary includes a resourceUri for fetching the full release body (release notes, packages, build information, custom fields). It is categorised as a Read tool in the Octopus Deploy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Octopus Deploy MCP Server MCP server in PolicyLayer and add a rule for find_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 Octopus Deploy MCP Server. Nothing to install.
find_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 find_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 find_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.
find_releases is provided by the Octopus Deploy MCP Server MCP server (octopusdeploy/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Octopus Deploy MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Octopus Deploy MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.