Tools Section
Route: /lenser/<handle>/ag/tools
The Tools section is the registry + assignment + audit surface for any callable capability outside the model itself: HTTP fetches, file IO, vector lookups, third-party APIs, internal RPCs.
Egress classes
| Class | Network access | Requires approval |
|---|---|---|
none | no network, pure CPU | no |
read | network read-only (GET) | no |
network | full HTTP (POST/PUT/PATCH) | yes |
mutation | writes to platform data | yes |
Higher classes force an approval gate before the call is dispatched. See Approvals Section.
Tabs
- Registry — every tool you've registered. Open the Register Tool drawer to add one.
- Assignments — allow/deny matrix for this agent. Open the Assign Tool drawer.
- Approval queue — tool calls waiting on a human gate.
- Invocation log — historical calls with args, result, latency. Click a row to open the Tool Invocation drawer.
Code-backed workflow
Source of truth: ToolsSection.tsx plus Register, Assign, Profile, and Invocation drawers. The implementation separates registry, assignment, policy profiles, approvals, and invocation history.
- Register a tool in the workspace registry.
- Assign the tool to the agent and decide whether it is allowed.
- Add a tool profile when the tool needs policy, auth, sandbox, or approval metadata.
- Review approval queue and invocation history after live runs.
Verification: a real tool call should appear in Tool Invocation and related Run Detail.