Get statistics about the remote zip archive.
AI agents call get_zip_statistics to retrieve information from RemoteZip MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves metadata about a zip archive. It has no side effects, does not extract files, does not modify the archive, and does not execute code or commands. It falls squarely within the Read category as a data retrieval operation with no capability to alter state or trigger external operations.
From the tool's definition Tool name 'get_zip_statistics' and description indicate it retrieves statistics about a remote zip archive without modifying, extracting, or deleting any data. The server context confirms this is a read-only operation for querying archive information.
Attacks that exploit this kind of access
Get statistics about the remote zip archive. It is categorised as a Read tool in the RemoteZip MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RemoteZip MCP Server MCP server in PolicyLayer and add a rule for get_zip_statistics: 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 RemoteZip MCP Server. Nothing to install.
get_zip_statistics 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 get_zip_statistics 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 get_zip_statistics. 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.
get_zip_statistics is provided by the RemoteZip MCP Server MCP server (yuriyo/remotezip-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 →