Authorization
The decision about whether an authenticated identity may perform a specific action on a specific resource. Authentication establishes who is asking; authorization decides what they are allowed to do.
Klyn perspective: For agents, authorization has to happen per action. Klyn checks protected operations against policy at the moment of action and records the decision, so permission to read a record never quietly becomes permission to change it.
Cascading revocation
Withdrawing authority from an agent or delegation so that the withdrawal also applies to every agent and grant that depends on it downstream. Without cascading revocation, a sub-agent can keep acting after its parent's access has ended.
Klyn perspective: Revocation is only real if the next protected operation fails. Teams using Klyn should test withdrawal on connected routes, including cached decisions, tokens and downstream sessions, and confirm the operation did not happen at the destination system.
Delegated authority
Permission that one party grants to another to act on its behalf within defined limits. In agentic systems, a person delegates to an agent, and that agent may delegate part of the task to another agent.
Klyn perspective: Delegated authority should get smaller as work moves downstream. Klyn's delegation controls give teams a place to define the limits of an assignment, such as resources, allowed operations, expiry and further delegation, and to trace each grant.
Delegation chain
The sequence of handoffs from the original human principal through one or more agents to the agent that finally performs an action. Each link should carry forward who authorized the work and the boundaries of that authority.
Klyn perspective: A helper agent investigating a bug has no reason to inherit deployment rights. Klyn helps teams follow the observed workflow through connected agents and tools, so authority can be checked at each protected step of the chain.
Just-in-time access
Granting access only when it is needed, for a specific task and a limited time, instead of keeping standing privileges. Just-in-time access shrinks the window in which a compromised or misdirected agent can cause harm.
Klyn perspective: Agents are well suited to just-in-time access because their tasks are discrete. Klyn favors authorization that is bound to a single request and expires quickly over broad, long-lived grants.
Least privilege
The principle that an identity should hold only the minimum access required for its task. For agents, least privilege applies to tools, data, operations and the right to delegate further.
Klyn perspective: Most agents run with broader access than their tasks require. Klyn's posture scoring ranks over-privileged agents by the damage they could do, so teams know which permissions to reduce first.
Mandate
A signed, verifiable statement of what a person authorized an agent to do, including constraints such as amount, merchant, scope or expiry. The Agent Payments Protocol (AP2) uses mandates as tamper-evident proof of user intent in agent-led payments.
Klyn perspective: A mandate helps only if it is verified. Teams adopting mandates should be clear about who signs and verifies them, and how each requested action is checked against the mandate before it executes.
Scoped, short-lived credentials
Credentials limited to specific resources and operations that expire after a short period. They reduce the value of a stolen token and limit what an agent can do if its instructions are manipulated.
Klyn perspective: In Klyn's execution integration, an allowed request receives a short-lived authorization bound to that request, which must be redeemed before the action runs. Reusing it, or changing the request, cannot turn one permission into another.
Token exchange
An OAuth pattern, defined in RFC 8693, for trading one security token for another with a different audience or scope. It is commonly used for on-behalf-of flows, where a service acts for a user with narrower rights than the original token carried.
Klyn perspective: Token exchange is a useful building block for agent delegation, provided each exchange narrows the scope. The receiving service still has to decide whether the specific action is allowed.