---
title: "Agent identity"
canonical_url: https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/
author: Jan Brennenstuhl
---

# Agent identity

How AI agents get scoped, revocable access to tools and services when they act on behalf of people.

These entries cover the access questions behind the [Agentic Identity Broker](https://www.janbrennenstuhl.eu/projects/agentic-identity-broker/), which Magnus Jungsbluth and I built for agents that act on behalf of people. Each one explains what the relevant IETF and Model Context Protocol (MCP) specifications actually require and where our broker design fits. The MCP specification still changes between revisions, so the MCP entry names the revision it describes.


## Entries

- [How does authorization work for MCP servers?](https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/mcp-authorization/) (2026-10-13, guide): In MCP revision 2026-07-28, a protected MCP server over HTTP is an OAuth 2.1 resource server that accepts only tokens issued for itself. Markdown: https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/mcp-authorization/index.md
- [How should people grant and revoke an agent's access?](https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/consent-and-revocation/) (2026-10-13, guide): People should grant an agent access per service with chosen permissions and an expiry, and be able to revoke that grant at any time. Markdown: https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/consent-and-revocation/index.md
- [How does OAuth 2.0 Token Exchange keep provider tokens away from agents?](https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/token-exchange/) (2026-10-13, guide): OAuth 2.0 Token Exchange (RFC 8693) lets a gateway trade an agent's token for a provider token, so the provider token never has to reach the agent. Markdown: https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/token-exchange/index.md
- [Should an agent use a robot account or delegated access?](https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/delegation-vs-robot-accounts/) (2026-10-13, guide): An agent that acts for a person should use delegated access that names both the person and the agent. Markdown: https://www.janbrennenstuhl.eu/knowledge-base/agent-identity/delegation-vs-robot-accounts/index.md