read_file
Read the contents of a file within the workspace. Access is restricted to allowed paths and file size limits.
This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/read-file.md
What read_file does on Terminal Guardian
AI agents call read_file to retrieve information from Terminal Guardian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_file is rated Low
This tool retrieves file contents without side effects. It is clearly a Read operation. Severity is low because file reading alone poses minimal risk in a sandboxed environment, though confidence is not perfect (0.95 rather than 1.0) because the actual risk depends on what files are in the 'allowed paths' list—if sensitive credentials or private keys are accessible, severity could increase, but based on the…
From the tool's definition Tool name is 'read_file' and description states it 'Read[s] the contents of a file' with no mention of modification, deletion, or execution. Access restrictions and file size limits further indicate this is a bounded read operation.
Attacks that exploit this kind of access
The rule that runs read_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_file, this is the rule to start with:
read_file is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Terminal Guardian, apply this rule, and every read_file call is checked against it from then on.
Questions about read_file
Read the contents of a file within the workspace. Access is restricted to allowed paths and file size limits. It is categorised as a Read tool in the Terminal Guardian MCP Server, which means it retrieves data without modifying state.
Register the Terminal Guardian MCP server in PolicyLayer and add a rule for read_file: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Terminal Guardian. Nothing to install.
read_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_file rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for read_file. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
read_file is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Terminal Guardian, and thousands of servers like it.
This server
Across the catalogue