search_offline_wikipedia
AI agents call search_offline_wikipedia to retrieve information from Local Search 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 a locally-indexed Wikipedia dataset using BM25 search. It retrieves data with no side effects—no creation, modification, deletion, code execution, or financial impact. The empty tool description reduces confidence slightly, but the unambiguous server context and naming convention make this clearly a Read category tool with low severity.
From the tool's definition Tool name 'search_offline_wikipedia' and server description indicate 'query Wikipedia without internet connectivity' and 'offline search' — characteristic read-only operations.
Attacks that exploit this kind of access
search_offline_wikipedia. It is categorised as a Read tool in the Local Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Local Search MCP Server MCP server in PolicyLayer and add a rule for search_offline_wikipedia: 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 Local Search MCP Server. Nothing to install.
search_offline_wikipedia 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_offline_wikipedia 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_offline_wikipedia. 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_offline_wikipedia is provided by the Local Search MCP Server MCP server (yuzuponikemi/localsearch-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 →