|Weaknesses||Lower legs, head|
|Out of Universe Information|
|Game||Prince of Persia: The Two Thrones|
- "Once the Vizier mastered the art of transforming people and animal, he turned his attention toward giving life to the lifeless. The Stone Guardian was his first attempt. Combining impenetrable granite from a nearby quarry with thick vines pillaged from the Hanging Gardens, this creature resembles a dark golem. The Vizier infused the stone with tremendous amounts of Sand, bringing it to life. The vines that twist around the creature become like muscles and veins, allowing the creature to move about like a man--- and a very large, very strong, and nearly indestructible man. However, the Vizier has expended so much effort in armoring the creature's body that he has neglected its extremities--- the legs and head are especially vulnerable."
- —Official Booklet Description
The Stone Guardian appears in the City Gardens of Babylon. This large, stone monster is made from stone and vines piercing through its skin. After driving it into a rage, the Prince climbs onto the beast and rides it into a gate.
The monster breaks down the gate, falls into the river water below and kills himself in the process, allowing the Prince to continue and kill the Stone Golem at the same time. Right after you kill him there is a Save Fountain through a small hole to your right after you climb the ladder.
A strategy similar to Klompa can be used for the Stone Guardian. Attack the back of its legs without being killed by its punches or kicks until it kneels and perform a Speed Kill to gain control. Ride it through the corridor-like river line, avoiding the corners until you reach the wooden gate.
The Stone Guardian will ram the gate and destroy it, dying on impact. If, while riding, you hit a wall head-on or bump into the corners too much, the Stone Guardian will fall back and ultimately crush the Prince, killing him and itself in the process.
- In Rival Swords, the Stone Guardian is called "Brute" (the same creature that appeared in Warrior Within). This was likely an error on part of the developers.