{"version":"2.1.238","anchor":"mcp-header-minting-commands-run-through-the-shared-trusted-c","canonical_anchor":"mcp-header-minting-commands-run-through-the-shared-trusted-c","heading":"MCP header-minting commands run through the shared trusted-command runner","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-header-minting-commands-run-through-the-shared-trusted-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP header-minting commands run through the shared trusted-command runner\n\nMCP header-minting commands now run with credentials stripped from their environment.\n\n**What**\n\nA `headersHelper` command declared by an MCP server no longer shells out directly with your full environment. It runs through the same runner used for other repo-declared commands, which picks the working directory from where the config lives and strips credential environment variables for project, plugin and additional-directory configs.\n\n**Details**\n\n- The working directory is the plugin root, the declaring directory, or the current directory, depending on where the config came from.\n- If the workspace has no saved trust decision, the helper is refused with a printed explanation rather than an exception, with a distinct message for sessions rooted at your home directory.\n- Failure messages are now written per reason, including a new \"did not return valid JSON\" case.\n\n**Evidence**\n\n`did not return valid JSON`\n\n- Area: MCP\n- Names: `headersHelper`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}