On the watch task path, this package can automatically fetch and execute the separately published @tokenfactory/acc-mcp-server through npx, passing it the runner token. The named integration appears purpose-related, but the automatic execution of uninspected code is not disclosed in the README; this meets the remote-code execution block rule.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user starts `acc-runner watch`, a task is handled, and the global `acc-mcp-server` binary is unavailable.
Mechanism
The task runner writes `.mcp.json`; its fallback config launches `npx -y @tokenfactory/acc-mcp-server` and supplies the session access token as an argument.
Attack narrative
When handling an assigned task, the runner configures an MCP server for Claude Code. If its binary is not already installed, the configuration invokes `npx -y` to fetch and run `@tokenfactory/acc-mcp-server`, passing the runner access token. The package source makes this fallback visible and ties it to the ACC feature, but the package does not declare or bundle that code, and its README does not disclose the automatic fetch and execution. This exposes a default task path to uninspected remote code with the runner token.
Evidence
dist/cli.jsdist/task-runner.js