Status: [UNTESTED] Endpoints found: https://localhost:8443/v1/token Source: https://github.com/JPaiv/Prokura # Prokura **Run-scoped Kubernetes identities for AI agents.** Prokura gives each AI agent a run-scoped Kubernetes identity. You define allowed tasks with `Envelope` resources. An envelope specifies: * which Kubernetes resources the task can access * which operations (`verbs`) are allowed * which namespaces it can use * whether approval is required * how long the permission is valid * how many API calls the run can make An agent or human uses its own credential to request a `Mandate`. A mandate is a short-lived token for one run of one envelope. The Prokura proxy sits in front of the Kubernetes API server. It validates the mandate and sends each request using an impersonated Kubernetes identity. The request includes the run ID, envelope, and original principal, so the action can be traced in the Kubernetes audit log. Prokura does not require an authorization webhook. It works with EKS, GKE, and AKS. It is also independent of the MCP gateway. You can use it with Traefik Hub, agentgateway, ToolHive, a Kubernetes MCP server, or another gateway. *Prokura* is the Nordic and German legal term for a commercial power of attorney: a limited authorization to act on someone's behalf. That is the idea behind the project. > **Status: pre-alpha, and not yet working.** The `Envelope` and `Mandate` API types exist. The controller, the proxy, and the token service do not. Everything below describes the intended design, and the [Roadmap](#roadmap) says what is actually built. Do not use Prokura for anything you care about yet. --- ## Why AI agents are often given a Kubernetes credential that is valid for many different tasks. The credential may live in the agent's environment, where a prompt injection could potentially access it. MCP gateways solve part of this problem. They can authorize individual tools and tasks using JWT claims. For example, Traefik uses TBAC, agentgateway uses CEL, and ToolHive uses Cedar. However, the Kubernetes API server does not know about task