Create a new release for an Octopus Deploy project This tool creates a new release for a project. The space name and project name are required. All other parameters are optional and will use Octopus defaults if not specified.
AI agents use create_release to create or update resources in Octopus Deploy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Octopus Deploy MCP Server environment.
This tool creates a new release within Octopus Deploy, which is a reversible modification of state. While it doesn't execute deployments itself, it creates deployment artifacts that can trigger downstream deployments. The high severity reflects that creating unintended releases in a DevOps platform could lead to accidental or malicious deployments.
From the tool's definition Tool name is 'create_release' and description states 'Create a new release for an Octopus Deploy project'. The verb 'create' and explicit action of creating a new release indicate this modifies state by adding a new deployable artifact.
Documented attack patterns abuse exactly the kind of access create_release 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 create_release:
{
"version": "1",
"default": "deny",
"tools": {
"create_release": {
"limits": [
{
"counter": "create_release_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_release stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new release for an Octopus Deploy project This tool creates a new release for a project. The space name and project name are required. All other parameters are optional and will use Octopus defaults if not specified. It is categorised as a Write tool in the Octopus Deploy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Octopus Deploy MCP Server MCP server in PolicyLayer and add a rule for create_release: 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.
create_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_release 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 create_release. 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.
create_release 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.