zip_extract_file
Extract a single file from a local ZIP archive to a local output directory (zip-slip safe). Deterministic, no network.
This record as markdown: /tools/io-github-homenshum-nodebench/zip-extract-file.md
What zip_extract_file does on Nodebench
AI agents use zip_extract_file to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why zip_extract_file is rated Medium
This tool writes files to the local filesystem by extracting from a ZIP archive. It creates/overwrites files at the target output directory. The description notes 'zip-slip safe', meaning path traversal is mitigated, but it still writes to disk. No deletion or irreversible destruction is implied, so Write is the appropriate category.
From the tool's definition Extract a single file from a local ZIP archive to a local output directory
Attacks that exploit this kind of access
The rule that runs zip_extract_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_extract_file, this is the rule to start with:
zip_extract_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every zip_extract_file call is checked against it from then on.
Questions about zip_extract_file
Extract a single file from a local ZIP archive to a local output directory (zip-slip safe). Deterministic, no network. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for zip_extract_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.
zip_extract_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zip_extract_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 zip_extract_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.
zip_extract_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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue