Skip to main content
TripleBits Apprentice - Software for Agents

Menu

Sign In Register

Filesystem, Shell, and Browser Tools (Apprentice MCP)

Built-in Apprentice MCP tools for files, shell commands, and browser automation that run inside the agent Docker container, with every tool listed by name.

1 views

Filesystem, Shell, and Browser Tools (Apprentice MCP)

These built-in tools let an agent act on files, run commands, reach the network, and drive a browser. They all run inside the agent's Docker container, not on your host.

Each family is gated by its own capability: Filesystem Tools, Shell Process Tools, Web Network Tools, and Browser Access. The agent sees only the primary directory and the host folders you mounted, with the read-only or read-write mode you set.

Where These Tools Run

Filesystem, shell, and browser tools execute inside the agent container. A volume named project mounted into the agent appears as ~/project inside the container. Read-only mounts block writes even if a tool tries. See Docker Runtime Isolation.

Filesystem Tools

  • read_file: read a file's contents.
  • write_file: create or overwrite a file.
  • edit_file: make a targeted edit to a file.
  • list_directory: list directory contents.
  • glob: find files by glob pattern.
  • grep: search file contents by pattern.

Filesystem tools require the Filesystem Tools capability. Writes also require a read-write mount.

Shell Process Tools

  • bash: run a command inside the container.

Shell process tools require the Shell Process Tools capability. Command rules and permission prompts still apply, so blocked commands can be denied even when the capability is on.

Web and Network Tools

Web fetch and network access are gated by the Web Network Tools capability. Website allow and block rules apply, and blocked rules take priority over allowed rules. Use this capability for agents that should fetch web content, and leave it off for agents that should stay offline.

Browser Tools

Browser automation is provided through a Playwright-based browser running in the container. The agent gets browser_ tools to navigate, click, type, read the page, take screenshots, and similar, plus two control tools:

  • browser_reset: reset the browser session.
  • browser_reconnect: reconnect to the browser if the session dropped.

Browser tools require the Browser Access capability and a working browser launch configuration. If launch is configured but the tools are blocked, the agent cannot drive the browser. See Configure Agent Capabilities.

MCP Control Tools

Two tools let an agent inspect and recover its own MCP connections:

  • apprentice_mcp_status: report the status of connected MCP servers.
  • apprentice_mcp_reconnect: attempt to reconnect MCP servers.

These help an agent continue when an external MCP server degrades mid-run.

Designing Around Filesystem and Shell

Good patterns:

  • Start with read-only mounts and enable writes only where edits are intended.
  • Keep Shell Process Tools off for analysis-only agents.
  • Use specific command and website rules instead of broad wildcards.
  • Enable Browser Access only for agents that genuinely need automation.

Next Step

Continue with Image and Gallery Tools for image generation and gallery file management.