When Scripture Becomes a Slogan
What happens when biblical truth is recruited into a national cause?
There is nothing wrong with a government official quoting Scripture.
Christians should welcome the reading of God’s Word in places where it is rarely heard. Military service, national defense, leadership, sacrifice, courage, and faith are all subjects about which the Bible has much to say.
But there is a danger Christians must be especially careful about: using Scripture to give divine authority to something Scripture never actually said.
The danger isn’t Scripture in public life. The danger is Scripture without context—Scripture recruited into a cause it never proclaimed.
In his recent “State of the Force” address, Secretary of Defense Pete Hegseth invoked Scripture several times while describing the mission and identity of America’s military. Some of what he said may resonate deeply with Christians. But several of the biblical passages he cited deserve something more than applause.
They deserve context.
And context matters because Scripture is not a collection of inspirational quotations waiting to be attached to whatever cause we happen to be promoting.
“Blessed Is the Nation”
Hegseth cited Psalm 33:12:
“Blessed is the nation whose God is the LORD.”
He then connected that verse to America’s founding and to the military’s present reliance upon God.
The problem isn’t the quotation. The problem is what happens when the verse becomes an unofficial theological description of America.
Psalm 33 isn’t describing the United States. It wasn’t written as a prophecy about America. And it isn’t teaching that any modern nation that invokes God thereby receives a divine guarantee of blessing.
The verse continues:
“Blessed is the nation whose God is the LORD, the people whom he has chosen as his heritage.”
The context is covenantal. The psalm celebrates the sovereign God of Israel, His righteousness, His steadfast love, His creation, and His chosen people.
A verse about God’s covenant people cannot be universalized to any nation without collapsing the distinction between Israel and every other state.
There is a difference between saying, “America should recognize God,” and saying, “America is the nation described in Psalm 33.”
The first is a theological exhortation. The second requires a biblical basis Psalm 33 does not provide.
And Christians should be cautious here because Scripture repeatedly warns against confusing God’s purposes with the purposes of a nation. Israel itself—God’s covenant people—was repeatedly judged when it presumed upon its relationship with God.
If God’s own covenant people could be judged, Christians should be reluctant to turn a verse about God’s chosen people into a declaration of America’s divine status.
“God Bless America” — Why Would He?
This is where another familiar phrase enters the conversation.
Americans love to say, “God bless America.” It appears on bumper stickers, podiums, flags, speeches, and military ceremonies.
But Christians should ask a deeper question:
Why would He? See HIPPOCRATIC PARTY® God Bless America? Why Would He?
God does not bless nations because they request it. God blesses nations when they repent, when they turn, when they humble themselves, when they obey.
“God bless America” is not a guarantee. It is a plea — and one that must be made with humility, not presumption.
The danger is assuming God’s blessing while rejecting God’s commands.
Israel made that mistake repeatedly. The prophets rebuked them for it repeatedly.
And if God did not bless His own covenant people when they hardened their hearts, Christians should be cautious about assuming He will bless any modern nation simply because it invokes His name.
The question is not, “Will God bless America?” The question is, “Is America blessable?”
That is a far more biblical question.
Isaiah Wasn’t Recruiting Soldiers
Near the end of his speech, Hegseth invoked Isaiah’s famous response:
“Here am I; send me.”
Then he applied it directly to military missions:
“Send me to fight the Red Coats. Send me to fight the Communists. Send me to fight the Islamists. Send me.”
It sounds powerful.
But Isaiah wasn’t volunteering for military service.
Isaiah 6 begins with Isaiah seeing the Lord “high and lifted up.” He becomes painfully aware of his own sinfulness. He confesses his uncleanness. His guilt is removed. Then God asks:
“Whom shall I send, and who will go for us?”
Isaiah answers:
“Here am I! Send me.”
Send him where?
To preach a message of judgment to God’s own people.
Isaiah’s calling is not a guarantee of victory, popularity, or success. It is obedience—and suffering. His ministry begins with rejection, not triumph.
Isaiah’s “send me” cannot legitimately be converted into a Christian battle cry for whatever military enemy happens to occupy America’s adversarial role at a given moment.
If anything, Isaiah’s calling should make us more humble about our ability to identify our own cause with God’s cause.
The Armor Is Not Military Hardware
Hegseth also invoked Paul’s phrase:
“Put on the full armor of God.”
It sounds tailor‑made for a military speech.
Except Paul tells us exactly what the armor is.
In Ephesians 6, Paul names it:
- the belt of truth
- the breastplate of righteousness
- shoes prepared with the gospel of peace
- the shield of faith
- the helmet of salvation
- the sword of the Spirit, which is the word of God
Notice something missing:
No rifle. No missile. No tank. No drone. No uniform.
Paul is writing pastoral instruction to a church, not military doctrine to a nation.
And the enemy he describes is not a foreign army:
“For we do not wrestle against flesh and blood…”
Paul’s point is almost the opposite of turning spiritual warfare into military warfare.
A Christian soldier may carry a physical weapon. But the “armor of God” is not a sanctified name for military equipment.
“The Lord Is on My Side”
Hegseth also quoted Psalm 118:
“The Lord is on my side; I will not fear.”
Again, the verse is true.
But biblical truth does not become our personal property simply because we quote it.
Psalm 118 is a song of thanksgiving and trust in God. Its central message is not, “God has endorsed my military operation.” It is a declaration that God’s steadfast love endures and that His people can trust Him even when surrounded by enemies.
There is a difference between saying, “I trust that God is with me,” and saying, “God is on our side.”
The first is faith. The second can become presumption.
History is littered with people who believed God was on their side:
- Crusaders
- Kings
- Empires
- Revolutionaries
- Confederates and Union soldiers alike
The problem isn’t that they prayed. The problem is that both sides cannot claim divine endorsement.
When nations claim “God is on our side,” they often stop asking whether they are on God’s.
When Scripture Is Misused in the Bible Itself
Misusing Scripture is not a modern problem. The Bible itself records several moments when Scripture—or God’s words—are twisted, weaponized, or taken out of context.
1. Satan in Genesis 3
The serpent quotes God selectively:
“Did God really say…?”
He distorts God’s command, minimizes the consequences, and reframes obedience as oppression. This is the first misuse of Scripture in history.
2. Satan Tempting Jesus (Matthew 4; Luke 4)
Satan quotes Psalm 91 to Jesus:
“He will command his angels concerning you…”
But he rips the verse from its covenant context and uses it to justify reckless self‑exaltation. Jesus responds with Scripture in context.
Misused Scripture is the devil’s oldest tactic.
3. Job’s Friends
Job’s friends repeatedly quote true theological statements—about God’s justice, righteousness, and judgment—but apply them wrongly to Job’s situation.
God rebukes them:
“You have not spoken of me what is right.” (Job 42:7)
Their error wasn’t the verses. It was the application.
These biblical examples remind us that quoting Scripture is not the same as obeying Scripture.
God Doesn’t Need a Public‑Relations Department
Hegseth’s speech emphasizes warriors, strength, lethality, victory, power, and deterrence. Those are legitimate subjects for a military leader.
But Christianity doesn’t need military language to make God sound powerful.
God doesn’t become more impressive when attached to a weapons system. He doesn’t become more sovereign when placed behind a flag. He doesn’t become more righteous when a government invokes His name.
The danger of nationalizing Scripture is that eventually the nation stops asking, “Are we following God?” Instead, it begins asking, “Is God blessing what we are doing?”
The first places the nation under God’s judgment. The second places God under the nation’s agenda.
The prophets consistently did the former.
They confronted kings. They challenged armies. They rebuked religious leaders. They condemned injustice. They warned nations that God would judge them.
They did not serve as chaplains to national self‑confidence.
The Christian Must Be Willing to Say “No”
There is a place for patriotism. There is a place for military service. There is a place for national defense. There is a place for courage, discipline, sacrifice, and strength.
But there is also a place for Christian skepticism when someone wraps a political or military objective in biblical language.
The Bible is not a decoration for the speech. It is the judge of the speech.
Christians should ask:
- What did this passage mean?
- Who was speaking?
- To whom?
- Under what covenant?
- What was happening in the surrounding verses?
- What did the original author intend?
- Would the meaning remain the same if our political opponent used it?
If the answer is no, perhaps we aren’t interpreting Scripture. Perhaps we’re recruiting it.
And Scripture doesn’t need to be recruited. It needs to be obeyed.
Isaiah said, “Here am I; send me.” But Isaiah first stood before a holy God, confessed his unworthiness, and listened for God’s command.
Before asking God to send us, we should make sure we are willing to go wherever He actually sends us.
Because Scripture was never given to prove that God is on our side. It was given to reveal whether we are on His.