This post helps MTG players understand the protection rules so they can stop arguing about “but it should work” and start playing the game that’s actually on the table.
TLDR
- Protection is easiest to remember as DEBT: it stops Damage, Enchant/Equip, Blocking, and Targeting from sources with the stated quality.
- It does not stop things that don’t do DEBT stuff, like “destroy all creatures,” “each player sacrifices,” or “all creatures get -2/-2.”
- If a spell is targeting something and that target becomes illegal (because it gained protection), the spell usually “fizzles” if all its targets are illegal.
- Auras and Equipment with the forbidden quality fall off (state-based actions), which is a fancy way of saying: “yes, immediately.”
Protection is one of those mechanics that sounds like invincibility, then quietly reminds you it’s a rules keyword, not a personal force field. This MTG protection ruling is about four specific protections, and your job is to figure out whether the thing hitting you is actually doing one of those four. Spoiler: half the time, it isn’t.
MTG protection ruling: remember DEBT
Protection from a quality (usually a color) means the object or player is protected from sources with that quality in four ways:
D: Damage
Damage from sources with that quality is prevented. This includes combat damage and noncombat damage.
E: Enchant/Equip (and Fortify)
You can’t have Auras of that quality attached to you, and you can’t be equipped (or fortified) by Equipment (or Fortifications) with that quality. If they’re already attached and you gain protection, they fall off.
B: Block
Creatures with protection can’t be blocked by creatures with the stated quality.
T: Target
You can’t be targeted by spells with that quality, or by abilities from sources with that quality.
If you only memorize one thing, make it DEBT. It’s the whole mechanic in four letters, which is good, because Magic already has enough reading.
What “that quality” actually means
Protection can name more than colors. It can be a card type, subtype, supertype, or even a player (yes, really). The key is always the same: protection cares about the source of the damage/ability/spell/attachment/blocker, and whether that source has the protected-against quality.
Two quick clarifications that catch people:
- Spells have qualities too. A red instant is still red while it’s on the stack, so protection from red stops it from targeting you.
- Protection isn’t “can’t be affected.” It’s only DEBT. If an effect doesn’t target, doesn’t deal damage, doesn’t attach, and doesn’t involve blocking, protection just sits there looking smug.
The most common “wait, why did my creature still die?” moments
1) Board wipes that destroy
“Destroy all creatures” does not target and does not deal damage. Protection does nothing here. Your creature still gets destroyed, and you still look betrayed by your own keyword.
2) Board wipes that deal damage
A damage-based wipe does get stopped by protection if the wipe’s source has the protected quality. So protection from red can save a creature from a red damage sweeper. This is the rare moment where protection feels like the superhero cape you thought you bought.
3) Sacrifice and -X/-X effects
“Each opponent sacrifices a creature” does not target. Neither does “Creatures get -2/-2.” Protection doesn’t stop either one. You are not protected from the concept of sadness.
4) “Damage can’t be prevented” effects
Protection prevents damage. If something says damage can’t be prevented, the damage part of protection can get turned off, while the rest of DEBT (like targeting) still works. That’s not protection being inconsistent. That’s Magic being Magic.
A 10-second protection check
When something happens, run this checklist:
- What’s the source? (spell, permanent, ability, creature in combat)
- Does the source have the stated quality? (color/type/etc.)
- Is it trying to do DEBT?
- Target you?
- Deal damage to you?
- Attach (Aura/Equipment/Fortification) to you?
- Block you?
If yes, protection applies. If no, protection does nothing, and you should immediately stop negotiating with the rules text.
If you want more “why is Commander like this” brain relief, these are worth a read:
FAQs
Does protection stop Wrath of God style wipes?
No. If it destroys without targeting or dealing damage, protection doesn’t help.
If my creature gains protection after being targeted, what happens?
That target becomes illegal. If all targets of the spell/ability are illegal, it won’t resolve and gets removed from the stack.
Do Auras and Equipment fall off immediately?
Functionally, yes. They become unattached as a state-based action, which happens before anyone gets to do much celebrating.
Is “protection from everything” actually everything?
It’s DEBT against everything: no targeting, no damage, no attachments, no blocking. But it still doesn’t stop non-DEBT effects like “sacrifice” or “destroy all creatures.”