Create compressed archives (ZIP, TAR, etc.) from files and directories
AI agents use compress_files 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.
Compression creates new archive files without permanently destroying original data and is fully reversible (archives can be extracted or deleted). This is a Write operation rather than Destructive. Severity is low because the blast radius is confined to workspace directory creation; archives don't expose system-level risks or bypass sandbox constraints.
From the tool's definition Tool description states it 'Create[s] compressed archives (ZIP, TAR, etc.) from files and directories' — a reversible creation operation that modifies the file system by adding new compressed archive files.
Attacks that exploit this kind of access
Create compressed archives (ZIP, TAR, etc.) from files and directories. 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 compress_files: 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.
compress_files 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 compress_files 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 compress_files. 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.
compress_files 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 →