zip_read_text_file

Read a text file inside a local ZIP archive and return bounded text. Deterministic, no network.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/zip-read-text-file.md

WHAT IT DOES

What zip_read_text_file does on Nodebench

AI agents call zip_read_text_file to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zip_read_text_file is rated Low

This tool retrieves content from a file within a ZIP archive without modifying, executing, or deleting anything. It is purely a data retrieval operation with deterministic, local-only behavior. The 'bounded text' return suggests safe output limitations. No network access and no side effects justify the 'Read' category with low severity.

From the tool's definition Tool name contains 'read' and description states 'Read a text file inside a local ZIP archive and return bounded text.' The operation is read-only with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zip_read_text_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zip_read_text_file, this is the rule to start with:

zip_read_text_file Allowed

zip_read_text_file is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zip_read_text_file": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every zip_read_text_file call is checked against it from then on.

FAQ

Questions about zip_read_text_file

What does the zip_read_text_file tool do? +

Read a text file inside a local ZIP archive and return bounded text. Deterministic, no network. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zip_read_text_file? +

Register the Nodebench MCP server in PolicyLayer and add a rule for zip_read_text_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 Nodebench. Nothing to install.

What risk level is zip_read_text_file? +

zip_read_text_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zip_read_text_file? +

Yes. Add a rate_limit block to the zip_read_text_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.

How do I block zip_read_text_file completely? +

Set action: deny in the PolicyLayer policy for zip_read_text_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.

What MCP server provides zip_read_text_file? +

zip_read_text_file is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

claude_read_file on Claude Bridge →browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →