staticx_upload_zip · StaticX MCP Server MCP: Risk & Policy

WHAT IT DOES

What staticx_upload_zip does on StaticX MCP Server

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

WHY IT NEEDS A POLICY

Why staticx_upload_zip needs a policy

This tool uploads and stores a ZIP artifact into a workspace, which constitutes reversible modification of project data. It does not execute code, delete resources, or move funds. While the uploaded content could theoretically be deployed via separate tools (staticx_deploy_project), the upload itself is a Write operation.

From the tool's definition Tool name 'staticx_upload_zip' and description 'Upload a built static site ZIP into a project workspace' indicate the tool creates/modifies project content through file upload.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

staticx_upload_zip Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "staticx_upload_zip": {
      "limits": [
        {
          "counter": "staticx_upload_zip_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches StaticX MCP Server, so you can run agents against it safely.

FAQ

Questions about staticx_upload_zip

What does the staticx_upload_zip tool do? +

Upload a built static site ZIP into a project workspace. The ZIP root should contain index.html or index.htm plus 404.html. It is categorised as a Write tool in the StaticX 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 staticx_upload_zip? +

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

What risk level is staticx_upload_zip? +

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

Can I rate-limit staticx_upload_zip? +

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

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

staticx_upload_zip is provided by the StaticX MCP Server MCP server (madprodworks-coder/staticx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.