arvan_iac_kube_linter

What arvan_iac_kube_linter does on ArvanCloud MCP Server

AI agents call arvan_iac_kube_linter to retrieve information from ArvanCloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why arvan_iac_kube_linter is rated Low

Kube-linter is a static analysis tool that inspects YAML manifests and reports security/correctness violations. It does not provision, delete, execute on clusters, or perform any side effects—only retrieves and analyzes configuration data. This is a pure read operation with minimal blast radius if misused by an AI agent (worst case: noisy or inaccurate linting output).

From the tool's definition Tool 'arvan_iac_kube_linter' performs linting (analysis/validation) of Kubernetes manifests. Linting is a read-only operation that analyzes code/configuration for issues without modifying, executing, or deleting resources.

The rule that runs arvan_iac_kube_linter safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ArvanCloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arvan_iac_kube_linter, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "arvan_iac_kube_linter": {}
  }
}

Questions about arvan_iac_kube_linter