List deployments in a space This tool lists deployments in a given space. The space name is required. When requesting latest deployment consider which deployment state the user is interested in (successful or all). Optional filters include: projects (array of project IDs), environments (array of ...
AI agents call list_deployments 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 deployment data without side effects. It performs a listing/filtering operation with no ability to create, modify, delete, or execute anything. The read-only nature is confirmed by the server's stated purpose.
From the tool's definition Tool name is 'list_deployments' and description states it 'lists deployments in a given space' with optional filters.
Documented attack patterns abuse exactly the kind of access list_deployments 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 list_deployments:
{
"version": "1",
"default": "deny",
"tools": {
"list_deployments": {}
}
}list_deployments 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.
List deployments in a space This tool lists deployments in a given space. The space name is required. When requesting latest deployment consider which deployment state the user is interested in (successful or all). Optional filters include: projects (array of project IDs), environments (array of environment IDs), tenants (array of tenant IDs), channels (array of channel IDs), taskState (one of: Canceled, Cancelling, Executing, Failed, Queued, Success, TimedOut), and take (number of results to return). 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 list_deployments: 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.
list_deployments 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_deployments 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_deployments. 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_deployments 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.