AI agents use archive_extract to create or update resources in LuzzyTool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LuzzyTool environment.
Extracting an archive writes files to the filesystem, which is a reversible Write operation (files can be deleted afterwards). While it could overwrite existing files, the description mentions zip-slip protection, reducing the risk of path traversal attacks. It does not delete or irreversibly destroy data, so Destructive does not apply.
From the tool's definition 解压归档文件到指定目录 (extract archive file to specified directory); 支持 zip/tar/tar.gz/tar.bz2/tar.xz; 内置 zip slip 路径穿越防护
Attacks that exploit this kind of access
【必须调用】解压归档文件到指定目录。支持 zip/tar/tar.gz/tar.bz2/tar.xz。自动检测格式,内置 zip slip 路径穿越防护和解压大小限制。. It is categorised as a Write tool in the LuzzyTool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for archive_extract: 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 LuzzyTool. Nothing to install.
archive_extract 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 archive_extract 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 archive_extract. 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.
archive_extract is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →