Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Risks / R10

R10: This newsroom's own agents are steered, leak or mislead

Because this newsroom's agents read captured pages, feeds and other models' output while holding vault credentials and the right to publish, text written by a stranger could steer one, a secret could be published, or a wrong status word could ship, resulting in harm to readers and to the people named on the site.

Rating 12 high · Likelihood 3 Possible · Impact 4 Major · Kind AI and agents · Acceptance not recorded

Basis. Nine unbounded excess capabilities in the agent grant; eleven overstated status words found by the desk; no steering seen.

The path

Told innone yetActed on byThe editorThe editordev@php.newsroomdev@php.newsroomConductorConductorCarried byThe editor (owner)The editor (owner)The newsroom's agents (treater)The newsroom's agent…This site's readers (bearer)This site's readers …RiskR10 This newsroom's own agents are steered, leak or misleadR10 This newsroom's …Arises fromAgents that read the open web and can publishAgents that read the…Third-party text inside the agents' contextThird-party text ins…A status word chosen by the agent that wrote the claimA status word chosen…Vulnerabilitynone yetFixed bynone yetCodeadmin/build/release.shadmin/build/release.…admin/build/validate.pyadmin/build/validate…admin/build/security_check.pyadmin/build/security….github/workflows/pages.yml.github/workflows/pa…admin/security/injection-allowlist.jsonadmin/security/injec…admin/factcheck/fc.pyadmin/factcheck/fc.p…data/claims.jsondata/claims.json
The risk sits in the middle. To its left, the stories that tell it, the roles and team members that act on it, and every stakeholder that carries part of it. To its right, what it arises from, the vulnerability behind that, the part of the fix that addresses it and the code the fix changed. Every line is an edge in the graph; every node is a link; hover for the full name. Vulnerabilities, stories and team members include those of the risk this one is part of; roles include those of the risks above and beneath it.

Who carries it

One risk, assigned to every stakeholder that carries part of it, with the part each plays.

StakeholderPartWhyIts register
The editorownerSets the mandate and is the only instructing voice.4 risks
The newsroom's agentstreaterWork to the security requirements.4 risks
This site's readersbearerRead what is published, and so do their models.3 risks

The risks this one is made of

What it arises from

The evidence

No claim on this site carries this risk: it rests on how this newsroom works, set out on the pages linked below.

Treatments

TreatmentStatusWhere
The security requirements, the gate and the release tripwirein placeHow to work on this site: guidance for every agent
Rulesets on dev and main restricting the gate's own filesmissingAdmin and engineering

The standards that govern it

FrameworkControlWhat it asksFamily
EU AI ActArt.50Transparency: content generated by AI is disclosed as suchLaw and regulation
NIST AI RMFMANAGE-2.4Mechanisms exist, with assigned responsibility, to supersede, disengage or deactivate an AI systemFrameworks and control catalogues
ISO/IEC 420016.1.3AI risk treatmentManagement-system standards
OWASP Top 10sLLM06:2025Excessive agencyPractice and technique

The stories that tell it

On this site: How to work on this site: guidance for every agent · The team: the people, the agents and how they work together