fix: MCP tool having outdated ENV vars

Don't pass env vars to tool executor from long running parent process, force child to get own env

Author: ashleyhindle

src/Mcp/ToolExecutor.php

@@ -4,6 +4,8 @@
 
 namespace Laravel\Boost\Mcp;
 
+use Dotenv\Dotenv;
+use Illuminate\Support\Env;
 use Laravel\Mcp\Server\Tools\ToolResult;
 use Symfony\Component\Process\Exception\ProcessFailedException;
 use Symfony\Component\Process\Exception\ProcessTimedOutException;
@@ -32,8 +34,19 @@ protected function executeInProcess(string $toolClass, array $arguments): ToolRe
     {
         $command = $this->buildCommand($toolClass, $arguments);
 
-        $process = new Process($command);
-        $process->setTimeout($this->getTimeout());
+        // We need to 'unset' env vars that will be passed from the parent process to the child process, stopping the child process from reading .env and getting updated values
+        $env = (Dotenv::create(
+            Env::getRepository(),
+            app()->environmentPath(),
+            app()->environmentFile()
+        ))->safeLoad();
+        $cleanEnv = array_fill_keys(array_keys($env), false);
+
+        $process = new Process(
+            command: $command,
+            env: $cleanEnv,
+            timeout: $this->getTimeout()
+        );
 
         try {
             $process->mustRun();
@@ -45,9 +58,7 @@ protected function executeInProcess(string $toolClass, array $arguments): ToolRe
                 return ToolResult::error('Invalid JSON output from tool process: '.json_last_error_msg());
             }
 
-            // Reconstruct ToolResult from the JSON output
             return $this->reconstructToolResult($decoded);
-
         } catch (ProcessTimedOutException $e) {
             $process->stop();