I'm having trouble understanding the question. Do you mean bona fide scripts (shell, perl, etc.), or do you mean configuration declarations contained in Puppet manifests (which are sometimes inaccurately called "scripts")? Only in the former case might Puppet Exec resources be relevant.
In any case, it sounds like you are asking for a way to have the puppet master directly modify another computer, without any active participation from the target computer. In general, that is flat impossible, with or without Puppet. Only if the master and target machine share a disk is it conceivable; that might be if the target node is in fact a VM hosted on the same hardware as the master, or if target node is diskless and the master can write to the network filesystem(s) that serves the target node. Even then, the manifests that you would use in such cases are fundamentally different from those you would use for a standard master / agent setup, or for direct application by the target node.
It is possible to use Puppet as part of a provisioning process, but except in special cases such as discussed above, they all involve Puppet code running on the target machine. A master does not need to be involved, though it is often convenient to use one, especially if the node will continue to be managed via that master after it is deployed.
John