AI agents call wikipedia_search to retrieve information from Web Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Wikipedia search retrieves publicly available encyclopedic information with no side effects, no code execution, no data modification, and no financial transactions. The tool only queries and returns data. While the tool description is empty, the name and server context strongly indicate a read-only search operation with minimal risk.
From the tool's definition Tool name 'wikipedia_search' indicates a search operation on Wikipedia. Parent server description explicitly lists 'text/news search' as a capability, and the sibling tools (fetch_page, groq_search, hackernews_search, package_search, etc.) are all Read…
Documented attack patterns abuse exactly the kind of access wikipedia_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wikipedia_search:
{
"version": "1",
"default": "deny",
"tools": {
"wikipedia_search": {}
}
}wikipedia_search 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.
wikipedia_search. It is categorised as a Read tool in the Web Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Web Search MCP server in PolicyLayer and add a rule for wikipedia_search: 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 Web Search MCP. Nothing to install.
wikipedia_search 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 wikipedia_search 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 wikipedia_search. 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.
wikipedia_search is provided by the Web Search MCP server (sydasif/web-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Search MCP, 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.
15 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.