AI agents call read_file to retrieve information from PSKit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays file contents with line numbering, which is a read-only query operation. There are no side effects, no data modification, no code execution, and no destructive actions. The 5-tier safety pipeline on the server further mitigates risk.
From the tool's definition Tool name is 'read_file' and description states 'Read a file with line numbers' - purely retrieves file content without modification or side effects.
Attacks that exploit this kind of access
Read a file with line numbers. It is categorised as a Read tool in the PSKit MCP Server, which means it retrieves data without modifying state.
Register the PSKit 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 PSKit. 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 PSKit MCP server (nickalus12/pskit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →