mcp7zop_remove_archive_items
AI agents call mcp7zop_remove_archive_items to permanently remove resources in Mcp7zOp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing items from an archive is a destructive operation that irreversibly deletes data. While confined to archive files rather than the live filesystem, the deletion cannot be undone through normal means. The high severity reflects that an AI agent with access could permanently lose data by removing archive contents without proper safeguards.
From the tool's definition Tool name 'mcp7zop_remove_archive_items' directly indicates deletion of archive contents. The verb 'remove' combined with 'archive_items' describes irreversible removal of data from 7-Zip archives.
Attacks that exploit this kind of access
mcp7zop_remove_archive_items. It is categorised as a Destructive tool in the Mcp7zOp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp7zOp MCP server in PolicyLayer and add a rule for mcp7zop_remove_archive_items: 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 Mcp7zOp. Nothing to install.
mcp7zop_remove_archive_items is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mcp7zop_remove_archive_items 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 mcp7zop_remove_archive_items. 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.
mcp7zop_remove_archive_items is provided by the Mcp7zOp MCP server (zv-louis/mcp7zop). 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 →