List all spaces in the Octopus Deploy instance. ${spacesDescription} Always use this tool first to check that the requested space exists.
AI agents call list_spaces 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 lists metadata about spaces in an Octopus Deploy instance. It has no side effects, performs no modifications, and poses minimal risk even if called by an AI agent. It is purely informational and diagnostic in nature, consistent with the server's stated read-only purpose.
From the tool's definition Tool name 'list_spaces' and description 'List all spaces' indicates a query/retrieval operation with no data modification. Server description emphasizes 'read-only access' and 'inspect, query, and diagnose.'
Documented attack patterns abuse exactly the kind of access list_spaces 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_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_spaces": {}
}
} list_spaces 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 all spaces in the Octopus Deploy instance. ${spacesDescription} Always use this tool first to check that the requested space exists. 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_spaces: 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_spaces 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_spaces 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_spaces. 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_spaces 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.