AI agents call archive_test 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 validates an archive file to check its integrity — no data is written, modified, or deleted. It is a purely read/verification operation with minimal blast radius.
From the tool's definition 测试归档文件完整性。检查压缩包是否损坏、文件是否可正常读取 (Tests archive file integrity. Checks if archive is corrupted and files can be read normally)
Attacks that exploit this kind of access
【验证操作】测试归档文件完整性。检查压缩包是否损坏、文件是否可正常读取。. 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_test: 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_test 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_test 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_test. 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_test 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 →