filesystem
tool judged 1% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2025-W38 | 1 | 1 |
| 2025-W50 | 1 | 1 |
| 2026-W01 | 3 | 1 |
| 2026-W03 | 2 | 1 |
| 2026-W04 | 1 | 1 |
| 2026-W06 | 1 | 1 |
| 2026-W08 | 1 | 1 |
| 2026-W11 | 2 | 2 |
| 2026-W13 | 1 | 1 |
| 2026-W21 | 1 | 1 |
| 2026-W24 | 1 | 1 |
| 2026-W26 | 1 | 1 |
| 2026-W28 | 1 | 1 |
| 2026-W29 | 1 | 1 |
| 2026-W33 | 2 | 1 |
| 2026-W34 | 1 | 1 |
| 2026-W37 | 4 | 3 |
| 2026-W39 | 1 | 1 |
| 2026-W40 | 6 | 2 |
| 2026-W41 | 3 | 3 |
In their words
Stall said the agents share a filesystem and can use it to exchange information, but developers cannot directly instruct one workflow subagent to message another through the API.
Earlier posts cover testing one decision at a time, what readers taught us about scoring, running the check in CI, and an MCP filesystem server.
Execution happens somewhere that isn’t your filesystem, with boundaries set before the code arrives rather than configured per run.
Local exposure: the server runs on your machine Many MCP servers run locally, which puts them next to your filesystem, your environment variables (where secrets live), and your local network.
Projects link to those files using filesystem hard links.
In December 2025 OWASP published the Top 10 for Agentic Applications 2026 (ASI01–ASI10), and 2025–2026 brought a run of real MCP CVEs: command injection in mcp-remote (CVE-2025-6514), an unauthenticated MCP Inspector (CVE-2025-49596), path and symlink bypasses in the Filesystem server (CVE-2025-53109/53110), and trusted-config mutation in Cursor ("MCPoison", CVE-2025-54136).
Not "usually." One boundary, deliberately ordinary stack Next.js + TypeScript at the front, FastAPI + Python behind it, PostgreSQL for state, Redis optional, local filesystem for binaries.
The code that touches reality (git, filesystem, tests, merge) is all deterministic Python.