AI agents call search_zim_file to retrieve information from ZIM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval from static content without side effects. Searching an offline archive poses minimal security risk—it cannot modify data, execute code, delete content, or move money. The blast radius of misuse is limited to potential information disclosure of publicly available content already in the archive.
From the tool's definition Tool name 'search_zim_file' and description 'Search within ZIM file content' indicate a query/retrieval operation. ZIM files are read-only offline content archives (Wikipedia, etc.). No creation, modification, deletion, or execution capability is described.
Documented attack patterns abuse exactly the kind of access search_zim_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZIM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_zim_file:
{
"version": "1",
"default": "deny",
"tools": {
"search_zim_file": {}
}
} search_zim_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search within ZIM file content. It is categorised as a Read tool in the ZIM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZIM MCP Server MCP server in PolicyLayer and add a rule for search_zim_file: 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 ZIM MCP Server. Nothing to install.
search_zim_file 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 search_zim_file 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 search_zim_file. 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.
search_zim_file is provided by the ZIM MCP Server MCP server (thinkinai-hackathon/zim-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ZIM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 ZIM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.