AGENT ACTION, read 13 Nov 2026
4 of 16 tools document stopping file read before it completes
Which tools can stop a file read?
4 of 16 tools document stopping file read before it completes: Noma Security, Island, Knostic and Pillar Security. 5 more do in part (Microsoft, Bay, Aim Security, CrowdStrike and Zenity).
What this action is
An agent opening a local file, including files outside the project it was started in.
Tool by tool
| Tool | Level | Note | Source |
|---|---|---|---|
| Noma Security | documented | Noma's public Claude Code plugin README documents hook-based evaluation of file reads (.env, SSH keys) with block, mask and ask policies (beta; fail-open on hook failure). | noma.security, 12 Nov 2026 |
| Island | documented | Says the file read on the endpoint can be blocked in an agent chain. | island.io, 12 Nov 2026 |
| Knostic | documented | Enforce mode blocks reads of files containing secrets. | knostic.ai, 12 Nov 2026 |
| Pillar Security | documented | Blocks reads of keys.env, SSH and cloud credentials from reaching external destinations. | pillar.security, 12 Nov 2026 |
| Microsoft | partial | Example blocks reading a local environment file after injection; general not file-specific. | learn.microsoft.com, 12 Nov 2026 |
| Bay | partial | Analyst profile lists files among evaluated action types; Bay pages do not detail file-read blocking. | softwareanalyst.substack.com, 12 Nov 2026 |
| Aim Security | partial | Dashboard flags risky settings such as writes outside the project; no documented block of file reads. | catonetworks.com, 12 Nov 2026 |
| CrowdStrike | partial | Sensor sees files agents access; blocking is documented via agent hooks in general terms. | crowdstrike.com, 12 Nov 2026 |
| Zenity | partial | Sensitive-file access followed by network action is blocked; plain file reads are monitored. | zenity.io, 12 Nov 2026 |
| Harmonic Security | none found | Documented controls cover prompts and tool calls; file reads not named. | docs.harmonicsecurity.app, 12 Nov 2026 |
| SentinelOne | none found | None found on 12 Nov 2026. | none found on 12 Nov 2026 |
| WitnessAI | none found | No file-read blocking documented. | none found on 12 Nov 2026 |
| Koi | none found | No file-read blocking documented. | paloaltonetworks.com, 12 Nov 2026 |
| Lasso Security | none found | File reads not named as a blockable action. | lasso.security, 12 Nov 2026 |
| LayerX | none found | None found on 12 Nov 2026. | none found on 12 Nov 2026 |
| Palo Alto Networks | none found | No file-read blocking documented. | paloaltonetworks.com, 12 Nov 2026 |
Ordered by documentation level, then by the site ranking. Read 13 Nov 2026.
Related: Action Control Matrix, how a cell is read.
About Bay
Bay ranks 2nd of 16 at 71.5, behind Microsoft at 75.0. Microsoft's lead over Bay comes from transparency (7 to 1) and policy and governance (9 to 6).
The other agent actions
Sources
- noma.security, read 12 Nov 2026
- github.com, read 12 Nov 2026
- island.io, read 12 Nov 2026
- knostic.ai, read 12 Nov 2026
- pillar.security, read 12 Nov 2026
- learn.microsoft.com, read 12 Nov 2026
- softwareanalyst.substack.com, read 12 Nov 2026
- catonetworks.com, read 12 Nov 2026
- crowdstrike.com, read 12 Nov 2026
- crowdstrike.com, read 12 Nov 2026
- zenity.io, read 12 Nov 2026
- docs.harmonicsecurity.app (checked, nothing found), read 12 Nov 2026
- paloaltonetworks.com (checked, nothing found), read 12 Nov 2026
- lasso.security (checked, nothing found), read 12 Nov 2026
- paloaltonetworks.com (checked, nothing found), read 12 Nov 2026
Last reviewed 13 Nov 2026.