Get the status of an ArgoCD application
AI agents call argocd-app-status to retrieve information from Kubernetes 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 information about an ArgoCD application's current state. It is a read-only operation with no side effects—it does not create, modify, delete, execute code, or commit financial obligations. The query pattern (status retrieval) is characteristic of Read category tools. Low severity reflects that misuse would only expose deployment information, not cause operational harm or data loss.
From the tool's definition Tool name 'argocd-app-status' and description 'Get the status of an ArgoCD application' indicate a query operation that retrieves application deployment status without modifying, executing, or deleting resources.
Attacks that exploit this kind of access
Get the status of an ArgoCD application. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for argocd-app-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 Kubernetes MCP Server. Nothing to install.
argocd-app-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 argocd-app-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 argocd-app-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.
argocd-app-status is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →