Kind: Conduit-run (local)
The Local Filesystem tool exposes read and write operations against a directory on the machine running Conduit. Every path is resolved and confined within the base directory you choose, so the model can only touch files inside it. It is the simplest way to let a model read project files, write patches, or search a codebase.
Operations
The tool registers the following MCP operations. The --read-only flag restricts it to the read operations only.
| Operation | Category | Description |
|---|---|---|
list-contents |
read | List a directory |
read-file |
read | Read a file (optionally a head/tail section) |
find |
read | Find files and directories |
grep |
read | Search file contents with a regex |
file-info |
read | Stat a file or directory |
write-file |
write | Write a file or edit a specific line |
create-directory |
write | Create a directory (recursively) |
copy-file |
write | Copy a file |
move-file |
write | Move or rename a file |
delete |
write | Delete a file or directory |
chmod |
write | Change file mode bits |
chown |
write | Change file owner and group |
Configuration
The tool's config in the console holds only an optional description. The actual base path and read/write mode are supplied when you connect it from Conduit, so they stay on the host that owns the files.
Connecting via Conduit
Create the tool in the console, then connect it from the machine that holds the files:
npx @infersec/conduit tool connect <tool-id> --key <api-key> --path ./ [--read-only]
| Flag / env | Required | Default | Notes |
|---|---|---|---|
<toolID> / TOOL_ID |
yes | - | Tool ID to connect |
--key / API_KEY |
yes | - | Infersec API key |
--path / TOOL_PATH |
no | . |
Base directory; all access is confined within it |
--read-only / READ_ONLY |
no | false |
Expose only the read operations |
--api-url / API_URL |
no | https://api.infersec.ai |
API base URL |
See the Conduit reference for installation and Docker usage.