AI agents call list_libraries to retrieve information from Mcpzim without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available offline archives without modifying, executing, or deleting anything. It follows the Read category pattern of non-destructive data queries. Lower confidence (0.85 rather than higher) due to the empty description, but the name and server context clearly indicate a simple listing operation.
From the tool's definition Tool name 'list_libraries' indicates listing/querying available ZIM file archives; the empty description combined with the server's read-only data retrieval pattern (search, get_article, get_main_page) strongly suggests this is an informational query with no…
Attacks that exploit this kind of access
list_libraries. It is categorised as a Read tool in the Mcpzim MCP Server, which means it retrieves data without modifying state.
Register the Mcpzim MCP server in PolicyLayer and add a rule for list_libraries: 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 Mcpzim. Nothing to install.
list_libraries 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_libraries 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_libraries. 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_libraries is provided by the Mcpzim MCP server (jasontitus/mcpzim). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_libraries is one line of Mcpzim's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →