Validate a local plugin or theme ZIP file
AI agents call validate_zip to retrieve information from QIT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs file inspection and validation checks on a locally-stored ZIP archive. It retrieves and analyzes the ZIP structure and contents to report validity status, but does not modify, execute, or delete the file. This is a pure read operation with minimal blast radius—worst case, it consumes computational resources or returns false validation results.
From the tool's definition Tool name 'validate_zip' and description 'Validate a local plugin or theme ZIP file' indicate inspection/verification of a file without modification. Validation is inherently a read-only operation that inspects ZIP contents against validation rules.
Attacks that exploit this kind of access
Validate a local plugin or theme ZIP file. It is categorised as a Read tool in the QIT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for validate_zip: 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 QIT MCP Server. Nothing to install.
validate_zip 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 validate_zip 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 validate_zip. 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.
validate_zip is provided by the QIT MCP Server MCP server (woocommerce/qit-mcp). 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 →