search_intelligence
Semantic search over DC Hub live intelligence corpus — news, M&A deals, facilities, and market analysis narratives. Natural-language query returns the most relevant cited records.
This record as markdown: /tools/cloud-dchub-mcp-server/search-intelligence.md
What search_intelligence does on Mcp Server
AI agents call search_intelligence 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 |
|---|---|---|---|
q | string | — | Alias for query |
limit | number | — | Max results to return, 1-15 (default 8) |
query | string | — | Natural-language query (required), e.g. "grids opening up for AI load in the Southeast" |
corpus | string | — | Optional corpus to restrict to: news | deals | facilities | market_narratives. CSV of several is allowed; default searches all. |
Parameters from the server's own tool schema.
Why search_intelligence is rated Low
This tool retrieves information through natural-language search and returns results. There is no indication of data modification, deletion, code execution, financial transactions, or irreversible actions. It is purely a data retrieval mechanism, fitting the Read category with low severity since misuse would only expose existing intelligence data rather than cause broader harm.
From the tool's definition Tool performs 'semantic search' and 'returns the most relevant cited records' — retrieves and queries data without modification. No side effects mentioned. The description indicates read-only access to a corpus of intelligence narratives.
Attacks that exploit this kind of access
The rule that runs search_intelligence 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 search_intelligence, this is the rule to start with:
search_intelligence 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 search_intelligence call is checked against it from then on.
Questions about search_intelligence
Semantic search over DC Hub live intelligence corpus — news, M&A deals, facilities, and market analysis narratives. Natural-language query returns the most relevant cited records. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
search_intelligence accepts 4 parameters: q, limit, 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 search_intelligence: 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.
search_intelligence 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_intelligence 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_intelligence. 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_intelligence 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