Guide · Local AI connector

Local AI connector: security and roll-out

For the person who reviews or approves the connector: what it reads, where it connects, which token it needs, and how to roll it out to a team.

How the data flows

What it reads from Azure DevOps

Work item state, type, dates, sprint and area path, estimates, board column and the blocked flag, with their state and sprint history. The team’s sprints, working days and areas. Named Agile Analytics settings only, such as the saved workflow mapping and the admin switch. The licence state the extension stores: the plan, the trial dates, and when the licence was last validated and the licence server last reached. From version 6.79.1, for the seat check: the plan’s access rule the extension stored, the organisation’s access list when the plan limits seats, and the Azure DevOps identity of the person whose token it is. These are used on the person’s computer for a yes or no.

What it never reads

Work item titles, descriptions, comments and tags, and who an item is assigned to. Never the licence activation token, the licence’s id or the organisation name on it. It never lists the extension’s settings, so it cannot see other values.

What the assistant sees

Numbers, dates, fixed words and ids, including work item ids, and on Premium and during the trial one link back to the matching view, built only from the organisation, project and team the person named. Never a title, a name or a comment, and nothing from the seat check. The assistant sends what it sees to its own provider, as it does with any prompt.

What Baytek receives

Nothing. No telemetry, no usage counts and no licence call: the licence is checked on the person’s computer from what the extension stores in Azure DevOps.

Where it connects

Two addresses

dev.azure.com and extmgmt.dev.azure.com, over HTTPS, with the person’s own access. No other address.

A fixed list of read requests

GET requests from a fixed list, plus one work item query that selects ids only. Anything not on the list is refused before it is sent, and the connector answers request-not-allowed. From version 6.79.1 it never follows a redirect, so a request only goes to the address the list checked, and it stops reading when the assistant cancels a question.

Nothing on disk

Nothing is written to disk. The token stays in memory and is never printed or logged. The team list, team areas and working days are kept in memory for 10 minutes and forgotten when the assistant closes.

Token scopes and least privilege

Exactly three scopes

Work Items: Read, Project and Team: Read, Extension Data: Read. Nothing else is needed, and none of them can change anything.

Least privilege

Create a token for the connector only, for the one organisation, with the shortest expiry your policy allows. Revoke it in Azure DevOps (User settings → Personal access tokens) when it is no longer needed.

The Azure CLI route

An Azure CLI sign-in is not narrowed by scopes: it carries the person’s full access. With it, the connector’s fixed list of read requests is what limits what it can reach. Where least privilege matters, use a token with the three scopes.

Approving it for a team

The command to allow

npx -y @baytekdev/agile-analytics-mcp. Claude Code on Windows starts it through cmd /c (cmd /c npx -y @baytekdev/agile-analytics-mcp). It needs Node.js 22 or later on each computer.

A fixed version

Teams that approve exact commands can fix the version: npx -y @baytekdev/agile-analytics-mcp@6.79.1. To move to a newer version, review it and change the number.

Where the token goes

In the assistant’s own secret or environment setting (the entry’s "env" block) or in the person’s user environment variable AZURE_DEVOPS_PAT. Never in a shared file: not in a workspace .vscode/mcp.json or a project .mcp.json, which are often shared or committed.

Turning it off

An extension admin can turn the connector off for the whole organisation in Configuration → General, “Allow the local AI connector”. It is on by default. The connector reads the switch before every answer and answers disabled-by-admin when it is off. Each change is recorded in the Admin activity log. The switch does not change anyone’s Azure DevOps permissions.

The licence

From connector version 6.78.1 it answers only while the organisation is on its trial or has a valid licence.

Who can use it

From connector version 6.79.1 it follows the extension’s own access rule: everyone during the trial, on Premium and on older plans open to the whole organisation; on Team and Business, only people who hold a seat (assigned by an extension admin in Configuration → Access Control) and extension admins. Anyone else gets no-seat. Earlier connector versions do not have this rule, so ask your team to run 6.79.1 or later.

Reporting a security problem

Email support@baytekdev.com with the subject line [SECURITY], or open a private security advisory on GitHub at github.com/MrHenrySword/agile-analytics-mcp/security/advisories/new. Baytek acknowledges receipt within three business days. The Security page has the full disclosure policy, and the Privacy page covers the connector too.

Need help?

Our support team is available Monday through Friday, 9 AM to 5 PM Pacific Time.