Concern 170 · Working draft · editorial review in progress

Third-party plug-in risk

Third-party plug-in risk arises when an AI application gives outside software access to information or actions.

Understanding the concern

A plug-in or tool can connect an assistant to email, files, calendars, or other services. Its usefulness depends on that access, but mistakes or malicious behavior can expose data or trigger unwanted changes. Trust in the AI model does not automatically extend to every connected tool.

Risks can come from the tool's code, the permissions it receives, or instructions in its descriptions and results. A popular framework does not make every extension safe. Permissions should match the task, and consequential actions need checks that do not rely only on model judgment.

An example

Giving an assistant a new tool is like handing a contractor a key: the important question is which doors it opens.

Illustrative unless identified as a documented case.

Words in plain English

AI
Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.
Model
The learned part of an AI system. It uses patterns found during training to produce an answer or prediction.

Evidence and its limits

The sources demonstrate different tool-mediated attack surfaces. They do not imply that all plug-ins or a named framework are unsafe.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

What can this plug-in read or change, and does it need all of that access?

Keep track of different views, what needs checking, and any next step in your own discussion notes.

Open discussion notes →
Principles for the conversation

Before you finish · reflect together

Virtues and principles to consider

Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.

Stewardship

Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.

Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.

Ask together: What are we responsible for caring for over time?

Prudence

Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.

Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.

Ask together: What is a careful next step, and when should we stop or change course?

Accountability

Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.

Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.

Ask together: Who will answer for the outcome and help put things right?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Major · 4/5
Likelihood
Documented at scale · 5/5
Time horizon
Now
Register risk score
20
About the register and scoring →
More ways to explore

Search for more writing

For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.

Explore a proposed use of AI →