Component

core/ai-tool/filesystem

A tool that gives an agent a file tree it can work in, listing, reading and, where the Aggregate allows it, writing files. Access is chosen by the developer and defaults to read-only, so the ability to write is granted deliberately rather than inherited, and the declared effect can be narrowed to match. Marked mutating by default, because a writable file tree outlives the invocation that changed it. The tree sits on a disk this component carries, so a file written in one call is still there for the next — which is why an agent that needs a working area to survive between calls is wired to this component rather than to a tool that keeps nothing. One instance holds that disk, so every call reaches the same files. Realized on Kubernetes via its Helm Recipe, which synthesizes that one instance with its own disk and a ClusterIP Service fronting it; helm-only. Exports the Service's host, port, endpoint and protocol to consumers via the uses topology, so an agent wires to the tool the same way it wires to any other service. An edge from the tool, on a socket the author names, delivers what its `inject:` block dictates, as variables or as files outside the tree, on every realization that runs the tool. The image serving the tool is the Release's, because this component packages no upstream product. Nothing renders until the Release sets `infra.image`. The component's own `inject:` block takes `env` and `file` entries too, and one reading a value of the tool alone replaces that value's default variable name.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:3814fafd302660d2aee9fca217afbf2b151eb6dabe3532e0be7a4749321af6aa
Published
2026-11-10T10:09:57Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:556cfdb4fd38abeb2ffda61c3a56bb8d1c3a3777d38ac81fe74d0cc2b315845b

Reference at this version

oci://hub.aggrega.ai/component/core/ai-tool/filesystem:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

Extends BaseComponents#/schemas/BaseToolParameter

NameTypeDefaultRequiredDescription
access_modestring (read_only | read_write)read_onlyyes—
side_effectsstring (mutating | read_only)mutatingyes—

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—noContainer image serving the file-tree tool over HTTP.
portinteger (min 1024, max 65535)8080noPort the tool listens on, and the port it publishes to consumers.
mount_pathstring/datanoDirectory inside the container where the tool's file tree is mounted. The image the Release names decides where it reads and writes, so this follows that image rather than the other way round.
storageobject—no—
computeobject—no—

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name an agent calls to work in the file tree. A consumer that composes its own address dials this name; one that does not reads `endpoint` instead.
portinteger—yesTCP port the file-tree API is accepted on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
endpointstring—yesFull base URL an agent sends list, read and write requests to, with the host and the port already composed. A consumer hands it to its tool client as the address it calls.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

env, file

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy