Protection From a Color in MTG: Damage, Enchanting, Blocking, and Targeting
TLDR: what protection from a color actually does
Protection from a color stops four main things involving sources of that color: damage, enchanting or attaching, blocking, and targeting. Players often remember these as DEBT. The full rule also covers Fortifications, so the more precise version is damage, Auras and attachments, blockers, and targets.
If you searched for protection from colors MTG rules because a creature “seemed immune” but still died, the important answer is that protection is not blanket immunity. It can prevent red damage, for example, without stopping a red effect that says “destroy all creatures.” It can make a target illegal without countering unrelated parts of a spell. It can stop a creature from being blocked before blockers are declared, but it does not retroactively make that creature unblocked afterward. Magic remains committed to making four rules look like one keyword.
The current Comprehensive Rules define protection through these specific restrictions rather than through a general concept of immunity. You can also find the latest rules documents through the official Magic rules hub.
The four parts of protection from colors in MTG
| Part | What protection stops | What it does not automatically stop |
|---|---|---|
| Damage | Damage from a source with the protected quality is prevented | Destroy effects, toughness reduction, sacrifice, or life loss |
| Enchanting and attaching | Matching Auras, Equipment, and Fortifications cannot remain attached | Attachments without the protected quality |
| Blocking | A creature with the protected quality cannot block the protected attacker | A block that was already legally declared |
| Targeting | Matching sources cannot target the protected object or player | Effects that do not target |
Damage
All damage that would be dealt to the protected creature or player by a source of the stated color is prevented. A creature with protection from red therefore takes no damage from a red creature in combat or from a red spell that deals damage. This works whether the damage effect targets, hits everything, or assigns combat damage.
Suppose a red sorcery deals 3 damage to each creature. It does not need to target for protection to matter: damage from the red spell to a creature with protection from red is still prevented. If an effect says damage cannot be prevented, however, that instruction defeats protection’s damage-prevention component.
Enchanting, equipping, and attaching
An Aura with the protected quality cannot enchant the protected object or player. Equipment and Fortifications with that quality cannot be attached to it. This is why DEBT is useful but slightly dated shorthand: the “E” is doing a suspicious amount of work, because the rule covers more than enchantments and Equipment.
Protection from red does not reject every piece of Equipment. Most Equipment is colorless, so protection from red normally has no objection. A red Equipment, by contrast, cannot be attached to a creature with protection from red. Protection from artifacts would stop Equipment based on its artifact quality regardless of its color.
Blocking
A creature with the protected quality cannot legally block an attacking creature with protection from that quality. A red-blue creature is red, so it cannot block an attacker with protection from red. The fact that it is also blue does not dilute its redness. Magic colors are memberships, not paint mixing.
This restriction is checked when blockers are declared. If the attacker gains protection from red after a red creature has already blocked it, the attacker remains blocked. Protection will prevent damage from the red blocker, but it does not rewind the block.
Targeting
A source with the protected quality cannot target the protected object or player. A red spell cannot target a creature with protection from red, and an activated or triggered ability from a red source cannot target it either. The relevant quality belongs to the source of the ability, not to a freestanding ability card floating somewhere in the rules void.
A spell or ability targets when its text says “target” or when a rule for a keyword or game action defines a target. An effect is not automatically targeting just because one permanent will be affected or one player makes a choice. Always check the current Oracle wording and any applicable keyword rules.
When protection is checked
Protection can matter at several different moments: while targets are chosen, when blockers are declared, as damage would be dealt, when an attachment’s legality is checked, and when a targeted spell or ability resolves. Identifying the current game moment usually resolves the argument faster than repeating “DEBT” with increasing confidence.
While casting a spell or activating an ability
You cannot choose an illegal target. If a creature already has protection from black, a black spell cannot be cast targeting that creature. Likewise, an ability from a black source cannot be activated with that creature as its target.
After a legal target gains protection
A target can be legal when a spell is cast and become illegal before that spell resolves. If you respond to a red targeted spell by giving its target protection from red, the target is illegal when the spell tries to resolve. If every target is illegal, the spell or ability does not resolve. If at least one target remains legal, it resolves and affects its legal targets as much as possible.
This distinction matters for spells with multiple targets. Protection may save one permanent without stopping the spell from affecting another. Protection is good; it is not a complimentary time machine.
During combat
Protection must exist when blockers are declared to prevent a matching creature from blocking. Giving an attacker protection after blockers are declared can still prevent matching-color combat damage, but the attacker remains blocked. An ordinary blocked creature without trample will not deal combat damage to the defending player merely because its blocker can no longer hurt it.
During state-based actions
If a permanent gains protection from the color or other quality of an Aura attached to it, that Aura is put into its owner’s graveyard as a state-based action. Matching Equipment and Fortifications become unattached but remain on the battlefield.
The difference comes from how unattached Auras behave. An Aura on the battlefield must be legally enchanting something, while Equipment can sit on the battlefield unattached without having an existential crisis.
What protection does not stop
The most common protection mistake is treating the ability as “this cannot be affected by red” or the equivalent for another color. That is not the rule. If an effect does not involve damage, an illegal attachment, blocking, or targeting, protection usually does nothing to it.
- A non-targeted effect that destroys all creatures can destroy a creature with protection from the spell’s color.
- An instruction that makes a player sacrifice a creature can get around that creature’s protection, provided the protected creature is not itself being targeted by the source.
- A non-targeted -X/-X effect can reduce the protected creature’s toughness. A creature with toughness 0 or less is put into its owner’s graveyard as a state-based action.
- Protection does not inherently stop counters from being placed on a permanent. It matters only if the counter-placing effect also does something protection forbids, such as targeting from a matching source.
- Protection does not prevent loss of life because loss of life is not damage.
- Protection does not remove counters already on a permanent or undo effects that have already changed it.
Wording matters. A black spell that says “target creature gets -4/-4” cannot target a creature with protection from black. A black spell that gives every creature -4/-4 without targeting can affect it. The result may look similar on the table, but the route through the rules is different.
How color and source checks work
Protection compares the stated quality with the source involved. For protection from a color, a multicolored object counts as every color it has. A red-blue spell is red, so it cannot target something with protection from red, and damage it would deal to that object is prevented.
Colorless is not a color. Protection from all colors therefore does not automatically protect against colorless sources. A colorless artifact creature can block a creature with protection from all colors unless another ability, such as protection from artifacts or protection from everything, prevents it.
Colors can also change. Use the source’s relevant characteristics at the time the game checks the interaction. If an effect makes a formerly red permanent blue, protection from red may no longer restrict its future targeting, blocking, attachment, or damage. Conversely, making a source red can cause protection from red to apply.
For players learning how multicolored objects are classified, this guide to Magic color combinations provides useful background. Color identity in Commander is a separate deck-construction concept; it does not replace an object’s actual color when protection is applied.
Protection, trample, and combat damage
Trample is the protection interaction most likely to produce a second argument immediately after the first one ends. Protection prevents damage, but it does not change how an attacking creature assigns trample damage.
When assigning trample damage, the attacker must assign lethal damage to its blockers before assigning excess damage to the defending player or battle. Damage-prevention effects are not considered when determining that lethal assignment. A 5/5 red creature with trample blocked by a 2/2 creature with protection from red can generally assign 2 damage to the blocker and 3 to the defending player. The 2 damage to the blocker is prevented, while the 3 assigned beyond it can still be dealt.
Protection therefore does not “absorb” all trample damage. It protects the creature from the matching source’s damage, but the combat damage assignment rules still allow excess damage to move past the blocker. For broader context on current combat procedures, see the MTG combat rule change explainer.
Common protection rulings at a glance
| Situation | Result |
|---|---|
| A red targeted damage spell versus protection from red | It cannot legally target the protected object or player. |
| A red spell damages every creature | Damage to creatures with protection from red is prevented. |
| A black spell destroys all creatures without targeting | Protection from black does not stop the destruction. |
| A global black effect gives creatures -X/-X | Protection does not stop it merely because the source is black. |
| A red-blue creature tries to block protection from red | The block is illegal because the creature is red. |
| A colorless artifact targets protection from red | Protection from red does not stop it merely for being an artifact. |
| A creature gains protection after being blocked | It remains blocked, but matching-source damage to it is prevented. |
| A matching Aura is already attached when protection is gained | The Aura is put into its owner’s graveyard as a state-based action. |
| Matching Equipment is attached when protection is gained | It becomes unattached and remains on the battlefield. |
| A matching targeted spell loses one of several targets | It can resolve for its remaining legal targets. |
Frequently confused protection questions
Does protection stop activated and triggered abilities?
Only when one of protection’s restrictions applies. An ability from a red source cannot target a creature with protection from red, and red-source damage is prevented. A non-targeted ability from that source that destroys all creatures or reduces toughness can still work.
Can a player have protection from a color?
Yes. The player cannot be targeted by matching sources, damage from those sources is prevented, and matching Auras cannot enchant that player. Blocking and Equipment restrictions normally have no practical application to a player.
Does protection stop sacrifice effects?
Usually not. If an effect instructs a player to sacrifice a creature without targeting that creature, the chosen creature’s protection does not help. Protection could still matter if the source first needs to target the protected player.
Is protection from everything the same as protection from all colors?
No. Protection from all colors addresses colored sources but does not include colorless sources merely because they are colorless. Protection from everything is broader and applies against objects regardless of their characteristic values. Neither phrase creates blanket immunity to non-targeted, non-damaging effects that protection does not cover.
The table-ready takeaway
When protection causes a dispute, do not ask whether the protected card is “affected.” Ask four narrower questions: Is damage being dealt? Is something trying to enchant or attach? Is a creature being declared as a blocker? Is a matching source targeting it? If the answer to all four is no, protection probably does not stop the effect.
Then check timing. Protection before targets or blockers are chosen can make those choices illegal. Protection gained later can invalidate a target, prevent upcoming damage, or remove an attachment, but it does not erase a legally declared block. That sequence is the difference between a clean ruling and three players pointing at the same keyword as though volume creates precedent.