Medium Risk

project_export_zip

Export the project directory to a zip archive in the workspace

How to control project_export_zip ↓

What project_export_zip does on 8th Wall MCP Server

AI agents use project_export_zip to create or update resources in 8th Wall MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 8th Wall MCP Server environment.

Medium Risk

Why project_export_zip needs a policy

The tool writes/creates a zip file in the workspace. This is reversible (the zip can be deleted), so it does not qualify as Destructive. It performs no read-only query, code execution, external command invocation, or financial operation.

From the tool's definition Tool exports project directory to a zip archive — creates a new file artifact (zip archive) in the workspace, modifying the filesystem state.

Documented attack patterns abuse exactly the kind of access project_export_zip gives an agent:

How to control project_export_zip

PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_export_zip:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "project_export_zip": {
      "limits": [
        {
          "counter": "project_export_zip_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

project_export_zip 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.

  1. Create a free account and register 8th Wall MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about project_export_zip

What does the project_export_zip tool do? +

Export the project directory to a zip archive in the workspace. It is categorised as a Write tool in the 8th Wall MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on project_export_zip? +

Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for project_export_zip: 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 8th Wall MCP Server. Nothing to install.

What risk level is project_export_zip? +

project_export_zip is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit project_export_zip? +

Yes. Add a rate_limit block to the project_export_zip 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 project_export_zip completely? +

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

project_export_zip is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 8th Wall MCP Server tool call.

Start from 8th Wall MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

64 8th Wall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.