MentorAgent 1.3.1 release notes
MentorAgent 1.3.1 fixes a security defect in action policies: who is affected, what to do if you cannot upgrade yet, and the new support policy.
On this page
MentorAgent 1.3.1 was published on NuGet on 14 November 2026 (UTC). It is a patch version: it fixes a security defect of severity S1 in action policies, and nothing else. See Security.
The five packages require each other at exactly this version: upgrade them together. MentorAgent 1.3.1 runs on .NET 10. To upgrade, see Upgrade from 1.3.0.
Highlights
Section titled “Highlights”- An action policy now decides for every agent. An action that a policy does not offer a user stays out of reach. That holds for specialists, team members and agent sources too, and for a call to the action by name.
- Earlier minor versions get no more fixes. Only the latest minor version gets fixes, security fixes included.
New features
Section titled “New features”This version adds no features.
Improvements
Section titled “Improvements”This version has no other improvements.
This version fixes one defect, a security defect: see Security.
Security
Section titled “Security”BUG-233 (S1), in Novior.MentorAgent. The advisory is GHSA-wqpr-h32x-xm2v (external site): severity High, CVSS 8.1, CWE-863 (incorrect authorization), with no CVE. It affects 1.2.0 and 1.3.0. Versions 1.0.x and 1.1.x had no action policies, so they are not affected.
What happened. In 1.2.0 and 1.3.0, a signed-in user could run an action that an IMentorActionPolicy did not offer them. This happened when the policy decided at MentorActionStage.Offer and checked something else at MentorActionStage.Call. The policy example in the 1.3.0 README did so. There were two ways through:
- Through another agent. The policies were asked at the offer only about the coordinator's actions. Specialists, team members and the agents of an
IMentorAgentSourcegot their tools by roles alone, so they could call such an action. - By name. On Path A, where MentorAgent builds the agent from your
ChatClient(see Model providers), an action left out at the offer was still known to the coordinator. A user could ask for it by name, and only the policy's answer at the call decided.
Who is not affected.
- An application whose policies answer at the call the same question that they answer at the offer. The policy example of these pages,
CaseTeamPolicy, does so. - An action protected by its roles,
RequiredRoles, or by anIMentorActionGovernor. - The coordinator on Path B, your own
AIAgent.
What changes in 1.3.1. The policies decide which tools every agent is offered. MentorAgent asks them once a turn, at the agent's first request, with its AgentKind and AgentName. A call to an action that they did not offer that agent in the turn is refused: Denied, with the reason code not-offered. MentorAgent refuses it before any confirmation box, and does not ask the policies about the call.
If you cannot upgrade yet. Make each policy answer at MentorActionStage.Call the question that it answers at MentorActionStage.Offer. Or protect the action with RequiredRoles, or with an IMentorActionGovernor. Where policies are asked shows both stages.
Earlier minor versions get no more fixes
Section titled “Earlier minor versions get no more fixes”With 1.3.1 the support policy changes. Only the latest minor version gets fixes, in its patch versions, and a security fix ships as soon as it is ready. Earlier minor versions get no more fixes, security fixes included. The security fixes promised for 1.0.x, 1.1.x and 1.2.x are withdrawn. Upgrade to the latest minor version, which is compatible with the earlier ones: see Versioning and support.
Breaking changes
Section titled “Breaking changes”This version has no intended breaking change, and the public API does not change. Two changes of behavior come with the fix:
- Fewer tools for other agents. With an action policy registered, specialists, team members and the agents of an
IMentorAgentSourceare offered only the tools that the policies offer the user, as the coordinator is. - A new reason code for some refusals. A call to an action that a policy did not offer in the turn now reaches an
IMentorActionObserverasDeniedwithnot-offered, notnot-authorized.
The steps are in Upgrade from 1.3.0.
Deprecations
Section titled “Deprecations”This version deprecates nothing.
Dependency updates
Section titled “Dependency updates”This version changes no dependency: they are the same as in 1.3.0.
Known issues
Section titled “Known issues”The defects that are still open in 1.3.1, with what to do about each one, are on the Known issues page, together with the prerelease packages and the package versions to pin. The limits that are not defects are in Known limitations.
Upgrade from 1.3.0
Section titled “Upgrade from 1.3.0”- Upgrade the five packages together. Each package requires the others at exactly its own version.
- Check what your policies offer to other agents. A policy that leaves an action out at the offer now leaves it out for specialists, team members and agent sources too. Check that each agent still gets the tools it needs.
- Check what reads the reason codes. A report or an alert that counts
not-authorizednow also needsnot-offered, for the calls to an action that a policy did not offer. - Update the links you write by hand. If a page links
MentorAgent.cssandMentorAgent.jsitself, as theindex.htmlof a Blazor WebAssembly client or of a .NET MAUI application does, change?v=1.3.0to?v=1.3.1in both links.
If you upgrade from 1.2.0, first read Upgrade from 1.2.0 in the 1.3.0 notes.
Full list of changes
Section titled “Full list of changes”Every entry of this version is in the 1.3.1 section of CHANGELOG.md (external site), which is also the release notes on NuGet (external site).
See also
Section titled “See also”- Release notes — Every stable MentorAgent version, newest first, with its date and what it brings; how versions are numbered and supported, and how dependencies are followed.
- MentorAgent 1.3.0 release notes — What MentorAgent 1.3.0 adds and fixes: actions turned on and off outside your code, tenants, any vector store, whole-conversation tests, and how to upgrade.
- Action policies and observers — The types that let your code decide on each action, record every decision of the gate, know who confirmed a call, and list the actions.
- Roles, confirmation and governance — Role checks and human-in-the-loop approval for AI agent tools in .NET, enforced in code on every channel and not in the prompt, and what stays in your code.
- Known issues — The open defects of the current MentorAgent version and how to avoid them, the prerelease packages it depends on, and the package versions to pin.
