AI agents call archive_list to retrieve information from LuzzyTool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and lists the contents of an archive file, optionally with metadata like size, modification time, and compression ratio. It performs no modifications, deletions, or executions. Pure read operation with minimal blast radius.
From the tool's definition 【查询操作】列出归档文件内容 — explicitly labeled as a query operation that lists archive contents
Attacks that exploit this kind of access
【查询操作】列出归档文件内容。verbose=true 时包含文件大小、修改时间、压缩比。. It is categorised as a Read tool in the LuzzyTool MCP Server, which means it retrieves data without modifying state.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for archive_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the archive_list 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_list. 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_list 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 →