semantic_search
Use for CONCEPTUAL / fuzzy questions where keyword filters fall short — semantic (meaning-based) retrieval across DC Hub's industry news, M&A deals, 21,000+ discovered facilities, and per-market DCPI deep-dive analysis narratives, ranked by relevance with citable source fields (news url/title, de...
This record as markdown: /tools/cloud-dchub-mcp-server/semantic-search.md
What semantic_search does on Mcp Server
AI agents call semantic_search to retrieve information from 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 |
|---|---|---|---|
k | number | — | Number of results, 1-15 (default 8) |
q | string | — | Natural-language query (required), e.g. "grids opening up for AI load in the Southeast" |
query | string | — | Alias for q |
corpus | string | — | Optional CSV of corpora: news_articles, deals, discovered_facilities, market_narratives (default: all) |
Parameters from the server's own tool schema.
Why semantic_search is rated Low
This tool retrieves and queries existing data (industry news, M&A deals, facility information, market analysis) using semantic search capabilities. It performs no modifications, deletions, or execution of external operations. The examples provided ('what is happening with...', 'deals involving...', 'why is...') are all read-only investigative queries.
From the tool's definition semantic_search performs CONCEPTUAL / fuzzy questions with semantic (meaning-based) retrieval across news, deals, facilities, and analysis narratives, ranked by relevance.
Attacks that exploit this kind of access
The rule that runs semantic_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For semantic_search, this is the rule to start with:
semantic_search 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 Mcp Server, apply this rule, and every semantic_search call is checked against it from then on.
Questions about semantic_search
Use for CONCEPTUAL / fuzzy questions where keyword filters fall short — semantic (meaning-based) retrieval across DC Hub's industry news, M&A deals, 21,000+ discovered facilities, and per-market DCPI deep-dive analysis narratives, ranked by relevance with citable source fields (news url/title, deal parties/value, facility name/location, deep-dive market/url). Examples: "what is happening with behind-the-meter gas for AI data centers?", "deals involving nuclear power for hyperscalers", "why is Northern Virginia constrained?" — semantic_search q="behind-the-meter gas for AI data centers". Params: q (required, natural-language query); corpus (optional CSV subset of news_articles,deals,discovered_facilities,market_narratives; default all); k (1-15, default 8). Returns {results:[{source_table, kind, text, score, cite:{…}}]}. Complements the exact-filter tools (get_news / list_transactions / search_facilities) with relevance ranking; for a full token-budgeted market briefing use get_market_context. Cite "DC Hub (dchub.cloud)". It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
semantic_search accepts 4 parameters: k, q, query, corpus. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for semantic_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 Mcp Server. Nothing to install.
semantic_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 semantic_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 semantic_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.
semantic_search is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue