1,425 Filesystem-Mutation Profiles: What to Check Before Giving Agents a Workspace
Filesystem-mutation profiles total 1,425, with 4,365 file-read signals and 3,321 file-write signals. Workspace boundaries are central to MCP adoption review.
Terminology
| Term | Meaning |
|---|---|
| Public Registry | Inspected MCP candidates searchable in the public Registry |
| Profile evidence | Inspection-profile aggregates used to interpret public candidates in more depth |
| Review/action rows | Entries in WARN, NEED_REVIEW, RESTRICT, or BLOCK that require reasoned adoption review |
Lead
Filesystem MCP servers are useful automation gateways, but they can touch secrets, configuration files, source code, and generated artifacts under the same local authority.
Key Findings
- Filesystem-mutation profiles total 1,425, with 4,365 file-read signals and 3,321 file-write signals. Workspace boundaries are central to MCP adoption review.
- The 20,629 public Registry entries and 11,627 profile-evidence rows answer different questions and should not be mixed casually.
- The observation is an adoption input, not a final approval for a specific environment.
- Counts are snapshot evidence, so adoption review should check the observation date before treating the number as current state.
Dataset
| Item | Value |
|---|---|
| Article date | 2026-05-02 |
| Public Registry snapshot | 20,629 entries, synced 2026-06-06T01:17:38.963Z |
| Detailed profile evidence | 11,627 rows, generated 2026-05-20/21 |
| Public disclosure level | Aggregates, distributions, anonymized observations, and operational interpretation |
Observed Metrics
| Metric | Value | Meaning |
|---|---|---|
| Filesystem mutation profiles | 1,425 | Capability near filesystem mutation |
| File read signal | 4,365 | Observation near file read access |
| File write signal | 3,321 | Observation near file write access |
What We Observed
Filesystem MCP servers are useful automation gateways, but they can touch secrets, configuration files, source code, and generated artifacts under the same local authority. This lens matters because MCP servers are not just plugins; they are bundles of authority exposed to an AI agent.
Practical Reading
Declare readable and writable paths, prevent access to HOME or secret stores outside the project, and require diff review for auto-editing workflows. Review should record execution location, destinations, data touched, and unresolved evidence, not only the server name or README.
Limits
- The evidence uses public aggregate data and anonymized observations, not internal detection mechanics.
- Counts are snapshot values and will change as the Registry updates.
- This is not a claim that any named MCP server is safe or unsafe.
Conclusion
Declare readable and writable paths, prevent access to HOME or secret stores outside the project, and require diff review for auto-editing workflows. Keeping this evidence in the intake record makes the review repeatable across teams and deployments.
MCP Guard continuously turns public Registry and profile evidence into adoption-review signals for MCP security teams.