read_input_file
Read a JSON file of circuit inputs from the user's machine so it can be validated and proved. Returns only the SIGNAL NAMES and value types found — never the values themselves, which stay local. Use it when a user references a file instead of typing values, then pass the same path to prove_circui...
This record as markdown: /tools/0gzk-mcp/read-input-file.md
What read_input_file does on 0gzk
AI agents call read_input_file to retrieve information from 0gzk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to a JSON file containing circuit inputs |
Parameters from the server's own tool schema.
Why read_input_file is rated Low
Even though read_input_file only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs read_input_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0gzk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_input_file, this is the rule to start with:
read_input_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 0gzk, apply this rule, and every read_input_file call is checked against it from then on.
Questions about read_input_file
Read a JSON file of circuit inputs from the user's machine so it can be validated and proved. Returns only the SIGNAL NAMES and value types found — never the values themselves, which stay local. Use it when a user references a file instead of typing values, then pass the same path to prove_circuit via inputFile. It is categorised as a Read tool in the 0gzk MCP Server, which means it retrieves data without modifying state.
read_input_file accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the 0gzk MCP server in PolicyLayer and add a rule for read_input_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 0gzk. Nothing to install.
read_input_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_input_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_input_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_input_file is provided by the 0gzk MCP server (@0gzk/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0gzk, and thousands of servers like it.
This server
Across the catalogue