Hmm, I seem to have misread your question. So if you want to read input you can use the Bash builtin read (see output of help read).
You can use read with a custom prompt -p and its output automatically goes into a (shell!) variable named REPLY, unless you give a different name.
read -p "enter file path : "
find "$REPLY" -size +1M -exec rm {} +
NB: I also replaced the \; by a + which should result in less invocations by find, but may be less portable.
The variable PATH has a special meaning and comes prepopulated. You don't say which shell this is, but the ground rules are the same in all of those I am aware of. The PATH environment variable is used to locate folders which contain executable files (binaries, scripts ...). These are then executable without giving their full or relative path.
Please check out this piece of documentation to learn more. Quote:
$PATH
Path to binaries, usually /usr/bin/, /usr/X11R6/bin/, /usr/local/bin, etc.
When given a command, the shell automatically does a hash table search
on the directories listed in the path for the executable. The path is
stored in the environmental variable, $PATH, a list of directories,
separated by colons. Normally, the system stores the $PATH definition
in /etc/profile and/or ~/.bashrc (see Appendix H).
bash$ echo $PATH
/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin
PATH=${PATH}:/opt/bin appends the /opt/bin directory to the current
path. In a script, it may be expedient to temporarily add a directory
to the path in this way. When the script exits, this restores the
original $PATH (a child process, such as a script, may not change the
environment of the parent process, the shell).
Note
The current "working directory", ./, is usually omitted from the
$PATH as a security measure.
Use echo "$PATH" to see the current contents of this variable in your running shell.