search_intelligence

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/search-intelligence.md

WHAT IT DOES

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.

RISK

Why search_intelligence is rated Low

Retrieves and queries data from intelligence databases without modifying, deleting, or executing operations.

From the tool's definition Semantic search over intelligence corpus; retrieval; returns records with sources.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

search_intelligence is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_intelligence": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about search_intelligence

What does the search_intelligence tool do? +

Semantic (meaning-based) search over DC Hub's live intelligence corpus — industry news, M&A deals, discovered facilities and per-market DCPI analysis narratives — returning the most relevant records with citable source fields. This is the agent-friendly alias over the SAME retrieval layer as semantic_search: same results, different call shape. It takes query plus human-readable corpus names (news | deals | facilities | market_narratives); semantic_search takes q plus the raw table names. Call ONE of them, not both. Params: query (required, natural language); corpus (optional CSV of the four names above, default all); limit (1-15, default 8). BEHAVIOUR: read-only — it writes nothing, and repeat calls with the same arguments return the same records. ACCESS: works with no key, but anonymous results come back as a TRIMMED PREVIEW; the session X-API-Key hydrates full depth per key, and the free tier is capped per day (call claim_free_key once — no email — if you do not hold a key). Do NOT use when you can filter exactly: search_facilities for structured facility filters, get_news for date/keyword news, list_transactions for deal filters — those match fields and return complete sets, where this ranks by meaning and returns a top-N. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does search_intelligence accept? +

search_intelligence accepts 4 parameters: q, limit, query, corpus. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_intelligence? +

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.

What risk level is search_intelligence? +

search_intelligence is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_intelligence? +

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.

How do I block search_intelligence completely? +

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.

What MCP server provides search_intelligence? +

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.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 88 Mcp Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →