Quick Verdict
Protection from a quality stops exactly four things from sources with that quality: Damage, Enchanting or Equipping, Blocking, and Targeting — the DEBT mnemonic. Everything else goes straight through. A protected creature can still be destroyed by a spell that does not target it, sacrificed, exiled, shrunk to zero toughness, or killed by a source that does not have the quality it is protected from.
Protection is the oldest defensive keyword in Magic and the one players most consistently overestimate. The word sounds absolute. The rule is not.
Protection from a quality stops exactly four things, and there is a mnemonic for them that has been passed around since the 1990s: DEBT.
Damage from sources with that quality is prevented. Enchanting and Equipping by that quality is impossible. Blocking by creatures with that quality is impossible. Targeting by spells and abilities with that quality is impossible.
That list is complete. It is not a summary, it is the whole rule. Anything a source with the quality does that is not damage, attachment, blocking or targeting works exactly as normal — which means a great many things that kill creatures kill protected creatures without noticing.
The rule: protection from X prevents damage, attachment, blocking and targeting from X. Nothing else.
The Rule: DEBT in Detail
Damage is prevented. All of it, from any source with that quality — combat damage, burn spells, ability damage. The damage is prevented, not redirected.
Enchanting and Equipping is impossible. Auras and Equipment with the quality cannot be attached. If one is already attached when protection arrives, it falls off.
Blocking is impossible. Creatures with the quality cannot block the protected creature. Note the direction: the protected creature can still be a blocker, and can still be blocked by creatures without that quality.
Targeting is impossible. Spells and abilities with the quality cannot choose it as a target. A spell already on the stack that becomes illegally targeted simply does not resolve.
The board wipe hole
The single most common protection mistake is assuming it survives a wrath. A spell reading 'destroy all creatures' targets nothing and deals no damage. Protection is completely blank against it, in every colour, including protection from everything. If your plan for surviving removal is protection, you do not have a plan for surviving board wipes.
What Protection Does Not Stop
Worth stating plainly, because this is the list that decides games:
Non-targeting destruction. Board wipes, "destroy all", "each player destroys".
Sacrifice. The controller performs it themselves. Protection is irrelevant.
Exile that does not target. Mass exile effects go straight through.
Toughness reduction. -X/-X and -1/-1 counters kill via state-based actions, not destruction or damage.
Anything from a source without the quality. Protection from red does nothing about blue, green, white, black, or — the big one — colourless.
Effects that change control, or that make its controller do something.
Protection asks one question: does this source have the quality? If the answer is no, protection was never in the conversation.
Protection vs Hexproof vs Ward vs Indestructible
Four defensive abilities that overlap and are constantly confused.
The last row is the one worth internalising. Protection is the only one of the four that is genuinely an offensive ability. A creature with protection from a colour cannot be blocked by that colour, which against a mono-coloured opponent makes it flatly unblockable. Our guides to hexproof vs shroud, ward and indestructible cover the other three columns in depth.
The Aura Trick
One of the oldest plays in Magic, and it follows directly from the E in DEBT.
Your opponent puts a removal Aura on your creature — a Pacifism effect, or something that steals it. You give your own creature protection from that Aura's colour. The Aura is now attached illegally, and state-based actions put it in the graveyard.
The same logic works on Equipment, and on your opponent's Auras attached to their creatures if you can grant protection at instant speed.
Protection as a combat trick
Mother of Runes and its many descendants are so highly valued because a one-mana 1/1 whose tap ability grants protection from a colour of your choice answers, at instant speed: the removal spell on the stack, the block that would kill your creature, and the combat damage from anything that already blocked. One activation, three different jobs. It is the most efficient protection effect ever printed and it is banned or restricted nowhere.
Protection From Everything
The extreme version, most famously on Progenitus, a ten-mana Hydra Avatar with protection from everything plus a shuffle-back replacement effect.
Protection from everything treats every quality as one it is protected from. Nothing can damage it, enchant it, equip it, block it, or target it — regardless of colour, type or source.
It is still not immune. Board wipes that do not target still destroy it, edicts still make its controller sacrifice it, and toughness reduction still works. Progenitus survives those specific cases only because of its separate shuffle-back ability, not because of its protection.
That distinction is the cleanest possible summary of the keyword: protection from everything is not protection from everything that kills creatures.
In Commander
Protection behaves differently in a four-player format for one obvious reason: there are more colours across the table.
Protection from red is excellent against one red opponent and nearly useless when the other three are white, blue and green. That makes fixed-colour protection weaker in Commander than in a duel, and makes choose a colour effects like Mother of Runes correspondingly stronger.
The offensive use holds up better. A creature with protection from a colour is unblockable by that player specifically, which in a format with commander damage means a reliable 21-damage clock aimed at whichever opponent shares that colour.
The main caution is the format's answer profile. Commander is full of board wipes, edicts and non-targeting removal, which are precisely the effects protection does nothing about. As pure insurance for a commander you cannot afford to lose, ward or hexproof usually does more work.
History
Protection dates to Alpha, making it one of the original keywords, though it was not formally keyworded and reminder-texted until later.
Its rules text has been revised several times to close ambiguities, and the modern DEBT formulation is the settled version. What has changed most is design frequency: protection is now used sparingly on new cards, because it creates unfun, binary board states — a creature that a whole deck simply cannot interact with is not an interesting game.
Its role has largely been taken over by ward, which taxes interaction instead of forbidding it, and by shorter-duration protection effects that only last a turn. Wizards has been explicit that this is deliberate: transactional protection produces better games than absolute protection.
Common Misconceptions
"Protection means it can't die." It stops four specific things. Board wipes, edicts and toughness reduction all work.
"Protection from red stops all removal." Only red removal. Colourless removal is completely unaffected.
"A protected creature can't block." It can. Protection stops creatures with the quality from blocking it.
"Protection prevents all damage." Only damage from sources with the quality.
"Protection from everything is unkillable." It is not. Non-targeting removal handles it.
"An Aura already on the creature stays." It falls off as a state-based action.
Conclusion: Ask What the Source Is
Protection is the keyword that most rewards reading carefully and most punishes reading quickly. Four letters cover the entire rule, and every argument about protection at a kitchen table comes down to somebody assuming a fifth.
The habit that fixes it is asking two questions in order. Does the source have the quality? And is what it is doing one of damage, attaching, blocking or targeting? If either answer is no, protection is not part of the interaction at all.
And use it forwards. Protection's best application has never been keeping a creature alive — the format is full of removal it cannot see. It is making a creature unblockable by the one player you needed to get through.
Citations & Resources
- Wizards of the Coast: Comprehensive Rules — protection
- Scryfall: Every card granting protection
- Scryfall: Protection from everything, including Progenitus
- Scryfall: Mother of Runes — the definitive protection engine
Related Guides
- The Ultimate MTG Keywords Glossary — every keyword, with a printable cheat sheet
- Hexproof vs Shroud — the targeting-only defences compared
- MTG Ward Explained — the mechanic that replaced protection in modern design
- MTG Indestructible Explained — what survives destruction, and what does not
- MTG State-Based Actions — why zero toughness beats every protective ability
- MTG Proliferate Explained — the non-targeting effect protection cannot see
- MTG Colors Explained — why choosing the right colour to be protected from matters
Frequently Asked Questions
🔗 Related Resources
More Reviews:
Related Articles
MTG Color Combination Names: Every Guild, Shard and Wedge (2026)
All 31 colour combinations and what players call them. The ten Ravnica guilds, the five Alara shards, the five Tarkir wedges, the four-colour Nephilim names, and why WUBRG is the order.
MTG Discover Explained: Rules, Best Cards, Cascade Compared (2026)
Discover N exiles until it finds a nonland card of mana value N or less, then lets you cast it free or keep it. The full rules, the three real differences from cascade, and why it got banned in Pioneer.
MTG Monarch and The Initiative Explained (Full Rules 2026)
Two designations that hand out free value and a target on your back. Full rules for monarch and the initiative, how each changes hands, and why the initiative got banned in two formats.