Use the env program. Env is a command that starts another program with a possibly modified environment. Since env is a program, it does not have access to the shell's built-in shells, aliases, or anything else.
This command starts the echo program, looking for it in your path to the command:
$ env echo foo
You can verify this by using strace to monitor system calls while running echo vs env echo :
$ strace -f -e trace=process bash -c 'echo foo' execve("/bin/bash", ["bash", "-c", "echo foo"], [/* 16 vars */]) = 0 arch_prctl(ARCH_SET_FS, 0x7f153fa14700) = 0 foo exit_group(0) = ? $ strace -f -e trace=process bash -c 'env echo foo' execve("/bin/bash", ["bash", "-c", "env echo foo"], [/* 16 vars */]) = 0 arch_prctl(ARCH_SET_FS, 0x7f474eb2e700) = 0 execve("/usr/bin/env", ["env", "echo", "foo"], [/* 16 vars */]) = 0 arch_prctl(ARCH_SET_FS, 0x7f60cad15700) = 0 execve("/usr/local/sbin/echo", ["echo", "foo"], [/* 16 vars */]) = -1 ENOENT (No such file or directory) execve("/usr/local/bin/echo", ["echo", "foo"], [/* 16 vars */]) = -1 ENOENT (No such file or directory) execve("/usr/sbin/echo", ["echo", "foo"], [/* 16 vars */]) = -1 ENOENT (No such file or directory) execve("/usr/bin/echo", ["echo", "foo"], [/* 16 vars */]) = -1 ENOENT (No such file or directory) execve("/sbin/echo", ["echo", "foo"], [/* 16 vars */]) = -1 ENOENT (No such file or directory) execve("/bin/echo", ["echo", "foo"], [/* 16 vars */]) = 0 arch_prctl(ARCH_SET_FS, 0x7f0146906700) = 0 foo exit_group(0) = ?