Code Execution & Workspace Tool

The File Read Tool

Return the contents of a file in the agent’s workspace, with optional line ranges, so an agent can inspect code, config, or data before it reasons about or changes it.

Explore VDF AI Agents
SandboxedRuns in an isolated workspace
GovernedEvery action logged
AssignableTo any engineering agent
100%On-premise capable
The Execution Gap

A suggestion isn’t a shipped change

An agent that can only propose code still leaves all the work to a human. To actually deliver, it needs a real, governed workspace where it can run code, edit files, test, and use Git — safely, and without touching anything you didn’t allow.

01

Read-only agents

Suggestions still require a human to run, test, and commit everything.

02

Unsafe execution

Running agent-generated code on real infrastructure is a security risk.

03

No verification

Without tests and builds, an agent can’t know its change works.

04

Ungoverned Git

Direct repo access with no policy or audit is a non-starter in the enterprise.

How the Tool Works

File Read, without the risk

Capability

What it does

Read a file from the agent workspace.

it reads a file from the agent’s workspace and returns its contents, optionally scoped to a line range.

Tool
File Read

Assignable to any agent

ReadScopedRangedLogged

How it works

Predictable, inspectable behavior

Designed to be reliable.

reads are confined to the sandboxed workspace and logged, so an agent sees only the files it is allowed to and every access is traceable.

Governed
Policy + Audit

Every call logged

ScopedLoggedGovernedOn-prem

Governance

Private, governed, on-premise

Runs inside your perimeter.

Execution runs in an isolated, on-premise sandbox scoped per tenant with full command and file audit logging, so an agent can do real work on your code without unsafe access or anything leaving your perimeter.

100%
On-Prem

Per-tenant, logged

On-premRBACAudit logSovereign
Inputs

Parameters

The file_read tool accepts these inputs when an agent calls it. Required inputs are flagged.

Name Type Required Description
path string Required Workspace-relative path of the file to read.
start_line integer Optional Optional first line to return.
end_line integer Optional Optional last line to return.
Where it pays back

Where File Read pays back

Code inspection

Read the function an agent is about to modify.

Config review

Load a config file to understand current settings.

Grounded edits

See exact current content before patching it.

Data loading

Read a small data file into a task.

How VDF AI connects it

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.

ROI Snapshot

What changes after you assign it

Faster
From suggestion to shipped
Verified
Changes tested before merge
Traceable
Every command audited
100%
Code never leaves your perimeter
FAQ

Questions about the File Read tool

What is the File Read tool?

It reads a file from the agent’s workspace and returns its contents, optionally scoped to a line range. 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.

Can it read outside the workspace?

No. Reads are confined to the agent’s sandboxed workspace and are audit-logged.

Can I read just part of a large file?

Yes. Provide start_line and end_line to return only the range you need.

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.

Put File Read to work

See the File Read tool assigned to an agent and orchestrated in a governed, on-premise network.