Hiya,
The default anti CSRF settings will only work with "standard" anti CSRF tokens, ie ones supported by HTML.
I'm pretty sure the meta tag is not a "standard" - I think your app will be using JavaScript to access it.
In Zest you can assign response values to variables.
So if 'name="_csrf" content="' only appears once in your doc then you can use "Assign variable via string delimiters" and use that string as the start and a since double quote as the end.
Is this for manual testing or for automation?
If its for automation (inc spidering and active scanning) then things might get a bit more complicated.
Cheers,
Simon