// SCAN REPORT

ZIP MCP Server

4 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

2 can modify or destroy data

2 read-only

4 tools total

Community server · catalogue entry verified 04/07/2026

How to control ZIP MCP Server ↓

TOOL MAP

What ZIP MCP Server exposes to your agents

Read (2) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous ZIP MCP Server tools

Write · Medium compress This tool creates a new ZIP archive from existing files/directories. Write · Medium decompress Decompression creates new files and directories on the filesystem.

2 of ZIP MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control ZIP MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and ZIP MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "compress": {
    "limits": [
      {
        "counter": "compress_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "echo": {
    "limits": [
      {
        "counter": "echo_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register ZIP MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZIP →

Instant setup, no code required.

FULL CATALOGUE

All 4 ZIP MCP Server tools

WRITE 2 tools

Write compress Compress local files or directories into a ZIP file Write decompress Decompress local ZIP file to specified directory

READ 2 tools

Read echo Return the input message (for testing) Read getZipInfo Get metadata information of a local ZIP file

FAQ

Questions about ZIP MCP Server

How do I prevent bulk modifications through ZIP MCP Server? +

The ZIP MCP Server server has 2 write tools including compress, decompress. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach ZIP MCP Server.

How many tools does the ZIP MCP Server MCP server expose? +

4 tools across 1 categories: Read. 2 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on ZIP MCP Server? +

Register the ZIP MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every ZIP MCP Server tool call.

Deterministic rules across all 4 ZIP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZIP →

Instant setup, no code required.

4 ZIP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.