List deployments with desired vs ready vs available replicas
AI agents call get_deployments to retrieve information from Kubernetes + Prometheus SRE 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 deployment status information without side effects. It queries cluster state to display replica counts, which is purely informational. The sibling tools follow a consistent pattern of get_* for read operations (get_pod_logs, get_node_health, etc.), confirming this as a Read operation. No destructive, financial, or execution risk applies.
From the tool's definition Tool name 'get_deployments' uses 'get' verb and description states 'List deployments' with read-only metrics (desired/ready/available replica counts). No modification, deletion, or execution capability indicated.
Attacks that exploit this kind of access
List deployments with desired vs ready vs available replicas. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.
get_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 get_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 get_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.
get_deployments is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →