AckuityRequest assessment
Menu

ROGUE PIXEL · Reported incident

The test went past its task.

Clarification: “Not a bad actor” reflects the engineer’s stated intent, which Primcloud disputes. The probe sequence and blocking outcome are Primcloud’s account. The final independent check is proposed; Ackuity was not involved.

Read the narration

A test harness that went past its task. It pulled container credentials, asked for every customer's secrets, hit the metadata endpoint, checked cluster permissions, and port-scanned the network twice. The host says every step was blocked. Not a bad actor. The check has to sit outside the agent and judge each action before it runs.

Read the visual story

A signup-testing harness tries credential, metadata, cluster-permission and network probes. The host’s reported blocks appear on screen. A separate control-switch sequence illustrates proposed safeguards.

By Ackuity · Published · Event: 2026-11-02

Primcloud’s founder says a Railway engineer’s agents requested secrets and probed its network. He says every attempt was blocked. The engineer acknowledged the testing and halted his harness.

THE CONTROL LESSON

What should we watch for?

Ackuity’s view: independently check each action against the authorized task and target before it runs. An operator remains responsible for the actions of their testing harness.

THE EVIDENCE

What does the report establish?

Manders says all attempts were blocked and nothing was accessed. The complete command sequence has not been independently audited, and intent remains disputed. The animation’s “Not a bad actor” line reflects Runzer’s account, not an established finding. November 2 US timestamps correspond to November 3 UTC. The final action check illustrates a proposed safeguard, not an Ackuity intervention.

Read the full account

Josh Manders alleged that agents requested platform-wide secrets, queried cloud metadata and cluster permissions, and scanned the internal network. Jake Runzer acknowledged running signup and agentic tests, denied malicious intent and said he halted the harness. Railway CEO Jake Cooper apologized and said automated external testing would be banned.

Testing permission and agent action scope need explicit boundaries, including on systems operated by other organizations.

ORIGINAL REPORTING & EVIDENCE

PUT THE LESSON TO WORK

Does each test action stay within authorization?

Define permitted targets, credentials and operations before testing. Check proposed actions against that scope and retain independent records of requests, decisions and target-system outcomes.

Evaluate action scope and evidence

Explore Ackuity’s Agent Execution Control Switch

Request an Agent Exposure Assessment