Ah, the intricacies of Entity Framework. If I understood correctly, you ave a model XX with property Description. Model XX is available to many users, but only some users should be able to access XX.Description, so you blank it out in MethodA for people without access. MethodA is not shown in the question, but from context I am concluding that MethodA returns a view capable of editing the object. When the view posts, it posts to MethodB, in charge of saving updates. You want to make sure the XX.Description remains intact if the user was an underprivileged user.
If my understanding is correct, the simplest way would be to have a MethodBPrivileged and a regular MethodB, where the former will update XX.Description, but the latter won't.
In Entity Framework jargon... I'm unsure as I avoid it like the plague. Can EF map 2 models to the same table? If it can, create 2 models: One that contains the Description property, and one that doesn't. Then, in the server's MethodA routine, by virtue of checking the logged-in privileges, determine which model to use and which view to send: A view that posts to MethodB, or a view that posts to MethodBPrivileged.