search_open_knowledge
Search bounded English Wikipedia metadata through the public Wikimedia API. Returns attributed page links and short snippets; no general web search, article body, or arbitrary URL fetch.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/search-open-knowledge.md
What search_open_knowledge does on Delx MCP Server
AI agents call search_open_knowledge to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Knowledge query, 1-120 characters. |
timeout | integer | — | Upstream timeout in seconds. |
max_records | integer | — | Maximum number of Wikipedia results. |
Parameters from the server's own tool schema.
Why search_open_knowledge is rated Low
This is a constrained read operation querying public Wikipedia metadata via Wikimedia API. The tool retrieves and presents information without creating, modifying, deleting, or executing code. The bounded scope (English Wikipedia metadata only) and explicit limitations further reduce risk profile to low severity.
From the tool's definition Search functionality returning "page links and short snippets" with no modification capability. Description explicitly states "no general web search, article body, or arbitrary URL fetch", confirming retrieval-only semantics.
Attacks that exploit this kind of access
The rule that runs search_open_knowledge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_open_knowledge, this is the rule to start with:
search_open_knowledge is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every search_open_knowledge call is checked against it from then on.
Questions about search_open_knowledge
Search bounded English Wikipedia metadata through the public Wikimedia API. Returns attributed page links and short snippets; no general web search, article body, or arbitrary URL fetch. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
search_open_knowledge accepts 3 parameters: query, timeout, max_records. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for search_open_knowledge: 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 Delx MCP Server. Nothing to install.
search_open_knowledge 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_open_knowledge 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_open_knowledge. 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_open_knowledge is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue