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