Authorizing a file-export tool isn't making it safe: Muse's 6.

Authorizing a file-export tool isn't making it safe: Muse's 6.8 GB filesystem export shows agents can assemble large, sensitive archives from files they can access. Treat file tools as resources: enforce path scope, a byte budget, a max-result count, and an output-shape check, and require explicit approval to expand any of those. If you don't impose those bounds, you invite context overflow, data leakage, and runaway cost from a single user action.