Get list of files in a remote zip archive.
AI agents call list_files 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 retrieves and lists file information from a remote zip archive without creating, modifying, deleting, or executing any data. It has no side effects and presents minimal security risk—the worst-case misuse would be reconnaissance of archive contents. Confidence is high because the description is clear and the operation is inherently read-only.
From the tool's definition Tool name 'list_files' and description 'Get list of files in a remote zip archive' indicate retrieval without modification. This is a query operation that returns metadata about archive contents.
Attacks that exploit this kind of access
Get list of files in a 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 list_files: 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.
list_files 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 list_files 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 list_files. 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.
list_files 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 →