Extract compressed archives (ZIP, TAR, GZ, BZ2, etc.)
AI agents use extract_archive to create or update resources in MCP Workspace Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Workspace Server environment.
Extracting an archive creates new files and directories on the filesystem, which is a reversible write operation. While it could potentially overwrite existing files (e.g., zip-slip attacks or collisions), the primary action is creating/writing files rather than deleting them.
From the tool's definition Extract compressed archives (ZIP, TAR, GZ, BZ2, etc.)
Attacks that exploit this kind of access
Extract compressed archives (ZIP, TAR, GZ, BZ2, etc.). It is categorised as a Write tool in the MCP Workspace Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Workspace Server MCP server in PolicyLayer and add a rule for extract_archive: 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 MCP Workspace Server. Nothing to install.
extract_archive 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 extract_archive 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 extract_archive. 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.
extract_archive is provided by the MCP Workspace Server MCP server (shayyeffet/ultimate_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →