duckduckgo.search.related_topics
Get DuckDuckGo related/disambiguation topics for a query — a flattened list of related concepts, categories, or alternate meanings, each with a title and DuckDuckGo link. Useful for exploring ambiguous or broad queries (e.g. a name that maps to multiple people, or a category like "coffee"). Data:...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/duckduckgo.search.related-topics.md
What duckduckgo.search.related_topics does on Apibase
AI agents call duckduckgo.search.related_topics to retrieve information from Apibase 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 | Search query or topic to look up (e.g. "Python programming language", "coffee") |
Parameters from the server's own tool schema.
Why duckduckgo.search.related_topics is rated Low
Retrieves public search disambiguation data with no side effects or authentication required.
From the tool's definition Get DuckDuckGo related/disambiguation topics for a query
Attacks that exploit this kind of access
The rule that runs duckduckgo.search.related_topics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duckduckgo.search.related_topics, this is the rule to start with:
duckduckgo.search.related_topics 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 Apibase, apply this rule, and every duckduckgo.search.related_topics call is checked against it from then on.
Questions about duckduckgo.search.related_topics
Get DuckDuckGo related/disambiguation topics for a query — a flattened list of related concepts, categories, or alternate meanings, each with a title and DuckDuckGo link. Useful for exploring ambiguous or broad queries (e.g. a name that maps to multiple people, or a category like "coffee"). Data: DuckDuckGo Instant Answer API (api.duckduckgo.com), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
duckduckgo.search.related_topics accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for duckduckgo.search.related_topics: 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 Apibase. Nothing to install.
duckduckgo.search.related_topics 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 duckduckgo.search.related_topics 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 duckduckgo.search.related_topics. 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.
duckduckgo.search.related_topics is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue