The TFS Work Item Read Tool
Reach the delivery data that never left your data centre: work items, projects, and repository summaries from Team Foundation Server and Azure DevOps Server, read over a token you control.
Agents can’t act on context they can’t reach
The systems that run regulated delivery are often the ones no SaaS assistant can touch: TFS boxes inside the perimeter. Their work items stay invisible to AI unless the AI comes to them.
Pasted snippets
Copied context is stale the moment it lands.
Swivel-chair work
People shuttle data between tools by hand.
Over-broad tokens
Shared credentials see far more than needed.
No audit trail
Nobody can say what a bot read, or when.
TFS Work Item Read, without the risk
Capability
What it does
Read on-prem TFS and Azure DevOps Server work items.
it reads work items, projects, and repository summaries from an on-premises TFS or Azure DevOps Server instance.
Assignable to any agent
How it works
Predictable, inspectable behavior
Designed to be reliable.
the connector authenticates with a server URL, collection, and personal access token stored in your vault, so reads work entirely inside your network and are logged per call.
Every call logged
Governance
Private, governed, on-premise
Runs inside your perimeter.
Server reads use the URL, collection, and personal access token you configured — held in your credential store, never in a prompt — and run entirely inside your network with per-call audit logging.
Per-tenant, logged
Parameters
The tfs_workitem_read tool accepts these inputs when an agent calls it. Required inputs are flagged.
default: 50 Optional Maximum work items to return.
How the TFS Work Item Read tool works in practice
TFS Work Item Read exists for the estate hosted assistants cannot reach: on-premises Team Foundation Server and Azure DevOps Server. Configured through the TFS connector, it reads work items, projects, and repository summaries over a token you issued.
Because VDF AI itself runs on-premise, the whole loop — agent, connector, server — can stay inside your network. That makes it one of the few ways to give AI visibility into regulated delivery without a single record crossing the boundary.
Cloud-side projects pair it with Azure DevOps Work Item Read; reporting flows hand its output to Document Generator for the status pack nobody has to assemble by hand.
Where TFS Work Item Read pays back
Legacy visibility
Give agents eyes on the server-based backlog.
Air-gapped status
Delivery reporting with zero cloud egress.
Migration prep
Inventory items before a move off TFS.
Audit answers
Trace a change to its original work item.
Assigned to agents, orchestrated as networks
On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.
- 1Industry Your sector Finance, healthcare, telecom, government, and more.
- 2Use Case A job to be done Concrete workflows the business needs solved.
- 3Agent A specialized worker Governed AI agents that execute the use case.
- 4Tool TFS Work Item Read The capability you assign to an agent.
- 5Network Agents, orchestrated Many use cases and agents, working as one.
What changes after you assign it
Questions about the TFS Work Item Read tool
What is the TFS Work Item Read tool?
It reads work items, projects, and repository summaries from an on-premises TFS or Azure DevOps Server instance. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.
Does anything leave our network?
No. The server, the token, and the VDF AI platform can all sit inside your perimeter, which is exactly the deployment this connector is built for.
Which server versions work?
On-premises Team Foundation Server and Azure DevOps Server instances reachable at the URL and collection you configure.
What inputs does the TFS Work Item Read tool need?
It requires project, and optionally accepts ids and limit. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.
Which tools pair well with TFS Work Item Read?
TFS Work Item Read is commonly assigned alongside Azure DevOps Work Item Read, Jira Semantic Search, and Github Repository Explorer. On VDF AI you compose several tools and agents into a single governed, on-premise network.
Does it run on-premise?
Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.
How do agents use it?
You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.
Assign TFS Work Item Read to these agents
These VDF AI agents can be assigned this tool. Open an agent to see the full toolkit it can run.
Tools that work well alongside this one
Where this tool delivers value
Put TFS Work Item Read to work
See the TFS Work Item Read tool assigned to an agent and orchestrated in a governed, on-premise network.