A second contact with the bat is not automatically an offence. A narrow wicket-guarding exception depends on purpose and sequence. The example below distinguishes a grounded ball stopped defensively from one deliberately struck again to create a running chance.
When the second contact is permitted
Under Law 34, Hit the ball twice, the limited exception applies when the batter acts solely to guard the wicket. The ball must already have been contacted, and the protective action must happen before a fielder touches it. The exception cannot be used to stop a catch. It is therefore the batter’s immediate defensive purpose—not simply the fact that the ball was touched twice—that is central.
Worked hypothetical example
Hypothetical: A batter plays a defensive stroke. The ball has clearly grounded, rolls back towards the stumps and is about to dislodge a bail. Before any fielder reaches or touches the ball, the batter places the bat in its path and stops it from hitting the wicket. The contact is solely to protect the wicket, not to send the ball away for runs, and no catch is being prevented. On these stated facts, the limited exception can apply, so the second contact is not automatically an offence.
When the protection does not apply
Consider a different hypothetical: after the first contact, the batter deliberately strikes the ball again towards an empty area to create a chance of running. That is not wicket protection; it is a purposeful second strike to influence play. The exception cannot be treated as general permission for repeated batting.
Officials must assess the actual purpose and sequence. A contact made with an unheld hand is outside the stated protection, and a second action intended to prevent a catch cannot rely on it. This explanation concerns the MCC Laws; competition playing conditions may vary. The guard case itself does not establish that any run is scored.