zip_outputs · DocAgent MCP: Risk & Policy

WHAT IT DOES

What zip_outputs does on DocAgent

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

WHY IT NEEDS A POLICY

Why zip_outputs needs a policy

This tool creates (writes) a new zip file from existing outputs, which is a reversible file operation. It does not delete data (not Destructive), execute code dynamically (not Execute), move money (not Financial), or merely read data (Write, not Read).

From the tool's definition Tool name 'zip_outputs' and description 'Create zip of all outputs' indicate file creation/archival operations that package existing documentation outputs into a compressed archive format.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zip_outputs Rate-limited

zip_outputs 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": {
    "zip_outputs": {
      "limits": [
        {
          "counter": "zip_outputs_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 DocAgent, so you can run agents against it safely.

FAQ

Questions about zip_outputs

What does the zip_outputs tool do? +

Create zip of all outputs. It is categorised as a Write tool in the DocAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zip_outputs? +

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

What risk level is zip_outputs? +

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

Can I rate-limit zip_outputs? +

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

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

zip_outputs is provided by the DocAgent MCP server (vinnyfds/docagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.