Fleet tools

What it is

A tool gives a fleet one named action. The fleet author declares allowed tools in TRIGGER.md.

Group	Tools
Network	`http_request`, `web_search`, `web_fetch`, `pushover`
Memory	`memory_store`, `memory_recall`, `memory_list`, `memory_forget`
Schedule	`cron_add`, `cron_list`, `cron_remove`, `cron_update`, `cron_run`, `cron_runs`
Delegation	`delegate`, `spawn`, `schedule`
Files	`file_read`, `file_write`, `file_append`, `file_delete`, `file_edit`, `file_read_hashed`, `file_edit_hashed`
Local work	`shell`, `git`, `calculator`, `image`
Browser	`browser`, `browser_open`, `screenshot`
Messaging	`message`

Why it exists

The allowlist limits what the fleet can do. Instructions in SKILL.md do not grant access by themselves.

How it behaves

The runtime owns the built-in tools. A fleet receives only names listed under x-agentsfleet.tools.

x-agentsfleet:
  tools:
    - http_request
    - memory_recall
  network:
    allow:
      - api.github.com

http_request also follows the network host list. Secret references are filled by the credential firewall during an approved outbound request. An unknown tool is skipped and records UZ-TOOL-005 in the activity stream. The run continues with the remaining valid tools.

Limits

http_request accepts only hosts allowed by the fleet policy. Responses allow up to 1 MiB. Hosted runners have no display. browser_open and screenshot can fail there; use them only with a suitable self-managed runner. web_fetch does not use the fleet host list. Use http_request when a host restriction is required. Remove a tool name from TRIGGER.md to revoke it. The next fleet update applies the new list to later runs.

Getting started

Fleets

Workspaces

Cost control

CLI reference

Updates

Fleet tools

Fleet tools

What it is

Why it exists

How it behaves

Limits

​Fleet tools

​What it is

​Why it exists

​How it behaves

​Limits

​Related pages

Fleet tools

What it is

Why it exists

How it behaves

Limits

Related pages