Get Kubernetes live status for a project and environment This tool retrieves the live status of Kubernetes resources for a specific project and environment. Optionally include a tenant ID for multi-tenant deployments.
AI agents call get_kubernetes_live_status 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 queries and retrieves status information about Kubernetes resources without modifying, deleting, or executing any operations. It is a diagnostic/inspection tool consistent with the server's stated purpose of enabling assistants to 'inspect, query, and diagnose problems.' The blast radius of misuse is minimal—an AI agent retrieving status information cannot cause harm. Classification: Read (low severity).
From the tool's definition Tool description states it 'retrieves the live status' of Kubernetes resources with 'no side effects' implied by the read-only framing of the server description: 'Provides read-only access to deployments, releases, projects, environments, and other DevOps…
Documented attack patterns abuse exactly the kind of access get_kubernetes_live_status 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 get_kubernetes_live_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_kubernetes_live_status": {}
}
}get_kubernetes_live_status 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.
Get Kubernetes live status for a project and environment This tool retrieves the live status of Kubernetes resources for a specific project and environment. Optionally include a tenant ID for multi-tenant deployments. 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 get_kubernetes_live_status: 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.
get_kubernetes_live_status 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 get_kubernetes_live_status 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 get_kubernetes_live_status. 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.
get_kubernetes_live_status 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.