Agent Tools

What Friday can actually do.

Tools are Friday's hands: they connect a natural-language request to finished work while keeping sensitive actions behind clear approval.

11Tool families
6Categories
AskSensitive actions

Files tools

Read, create, and update workspace content while keeping file operations visible and permission-aware.

01

Read / write / edit files

Open, create, and modify workspace files with safety checks and approval prompts before changes.

02

Apply patch

Make precise, surgical edits to existing files when a targeted diff is safer than rewriting content.

Shell tools

Run commands and manage longer processes when a task needs the local development environment.

01

Run commands & processes

Execute shell commands and longer-running processes to build, test, inspect, or automate work.

Web tools

Research current information and work through browser-based tasks with the right access boundaries.

01

Web search

Look things up on the internet when a request needs fresh or verifiable information.

02

Web fetch

Pull readable content from a specific page or URL and treat it as evidence for the answer.

03

Web browser

Drive a real browser to interact with pages when simple fetching is not enough.

Media tools

Create images and other rich assets through the media providers configured in Friday.

01

Create image

Generate images from text descriptions using the configured text-to-image provider and model.

Automation tools

Schedule recurring work and health checks so suitable tasks can continue in the background.

01

Schedule (cron)

Create, update, pause, resume, list, delete, and run scheduled assistant jobs.

Extension tools

Add reusable skills, MCP servers, and specialist tool surfaces without changing the core assistant.

01

Load skills

Pull in reusable skill instructions, references, templates, schemas, or optional executable behavior.

02

Subagents

Spin up focused helper agents for independent parts of larger work.

03

MCP tools

Use tools exposed by connected Model Context Protocol servers.

From request to verified result.

Tool choice follows the task, available context, and permission policy at every step.

  1. 01

    Policy check

    Friday decides whether a tool is useful and keeps direct answers tool-free.

  2. 02

    Candidate filtering

    Permission boundaries narrow the available files, commands, accounts, and services.

  3. 03

    Ranking

    The assistant chooses the tool that best fits the requested outcome and current context.

  4. 04

    Approval

    Sensitive writes, deletions, publishing, messages, and private data access pause for confirmation.

  5. 05

    Verification

    Friday checks the result and returns a concrete answer, artifact, or completed action.

Permissioned actions

Friday acts, but you stay in control.

The assistant will not send messages, change records, delete data, or touch production systems without clear authorization.