By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Audience binding with resource indicators

Clients send the resource parameter so each token is minted for one specific MCP server, and servers must reject tokens meant for anyone else. This stops a malicious server from replaying a token it received against another service. Check that both your clients and your servers enforce audience validation.

Read in this order

  1. OfficialRFC 8707: Resource Indicators for OAuth 2.0Start here: the resource parameter that ties a token to one server.
  2. OfficialMCP security best practicesMCP's own guidance on audience checks and the attacks they prevent.
  3. OfficialRFC 9068: JWT Profile for OAuth 2.0 Access TokensWhat a JWT access token should contain so servers can validate audience.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.