Adjust an existing customer feature toggle in an Octopus Deploy project. Narrow surface — flip an environment on/off, change rollout percentages, or update the toggle-level description / default state. Internally fetches the current toggle, applies your patches in memory, and PUTs the merged body...
AI agents use update_feature_toggle 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 or modifies data reversibly without deleting data or executing arbitrary code. While feature toggles control application behavior, the tool itself only adjusts toggle configuration metadata and state percentages—changes that can be undone or corrected through the UI or subsequent calls.
From the tool's definition Tool description states it "Adjust[s] an existing customer feature toggle" and "applies your patches" via PUT operations.
Documented attack patterns abuse exactly the kind of access update_feature_toggle 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 update_feature_toggle:
{
"version": "1",
"default": "deny",
"tools": {
"update_feature_toggle": {
"limits": [
{
"counter": "update_feature_toggle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_feature_toggle 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.
Adjust an existing customer feature toggle in an Octopus Deploy project. Narrow surface — flip an environment on/off, change rollout percentages, or update the toggle-level description / default state. Internally fetches the current toggle, applies your patches in memory, and PUTs the merged body, so unmentioned environments and unmentioned fields are preserved. Deliberately not exposed: name/slug rename, tag changes, rollout group attach/detach, tenant targeting, segments, minimum version, adding or removing environment configurations entirely. For those, use the Octopus UI. Patches that reference an environment not already configured on the toggle are rejected with reason: environment_not_configured. The tool does not add new environment configurations. 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 update_feature_toggle: 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.
update_feature_toggle 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 update_feature_toggle 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 update_feature_toggle. 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.
update_feature_toggle 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.