AI agents use archive_create 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.
This tool creates new archive files, which is a reversible write operation. While it packages existing data into a new format, the original files remain intact and the operation can be undone by deleting the created archive. It is not destructive (doesn't delete originals), not execute (doesn't run arbitrary commands), and not financial.
From the tool's definition Tool name 'archive_create' and description states it creates compressed archive files (creates zip/tar/tar.gz/tar.bz2/tar.xz formats), packaging multiple files and directories into a single compressed file.
Attacks that exploit this kind of access
【必须调用】创建压缩归档文件。支持 zip/tar/tar.gz/tar.bz2/tar.xz 格式。可将多个文件和目录打包为一个压缩文件,支持压缩级别设置。. 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_create: 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_create 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_create 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_create. 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_create 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 →