search.semantic.web
Neural/semantic web search — finds conceptually related pages, not just keyword matches. Supports category filters (company, research paper, news, people, tweet), domain filtering, date range. Returns relevance scores and highlighted excerpts (Exa)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/search.semantic.web.md
What search.semantic.web does on Apibase
AI agents call search.semantic.web 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 |
|---|---|---|---|
type | string | — | Search type: "auto" (balanced), "neural" (semantic similarity), "keyword" (traditional). Default: auto |
query | string | Yes | Natural language search query — Exa finds semantically related pages, not just keyword matches |
category | string | — | Category filter for specialized indexes (optional) |
num_results | integer | — | Number of results (default 10, max 25) |
include_text | boolean | — | Include full extracted page text in results (default false — saves tokens) |
exclude_domains | array | — | Exclude results from these domains |
include_domains | array | — | Only include results from these domains (e.g. ["arxiv.org"]) |
end_published_date | string | — | Filter: only results published before this date |
include_highlights | boolean | — | Include key sentence highlights (default true) |
start_published_date | string | — | Filter: only results published after this date (ISO format, e.g. "2025-01-01") |
Parameters from the server's own tool schema.
Why search.semantic.web is rated Low
Performs read-only semantic search with filtering; retrieves information without side effects or state changes.
From the tool's definition web search, finds pages, returns excerpts, no modification or execution
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs search.semantic.web 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 search.semantic.web, this is the rule to start with:
search.semantic.web 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 search.semantic.web call is checked against it from then on.
Questions about search.semantic.web
Neural/semantic web search — finds conceptually related pages, not just keyword matches. Supports category filters (company, research paper, news, people, tweet), domain filtering, date range. Returns relevance scores and highlighted excerpts (Exa). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
search.semantic.web accepts 10 parameters: type, query, category, num_results, include_text, exclude_domains, include_domains, end_published_date, include_highlights, start_published_date. 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 search.semantic.web: 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.
search.semantic.web 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.semantic.web 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.semantic.web. 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.semantic.web 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