get_market_intel
Use when a user asks about ONE data-center market — vacancy, capacity pricing, supply pipeline, dominant operators, YoY growth — across any of 300+ markets. Example: "What is Northern Virginia's vacancy rate, $/MW-day pricing, and current DCPI verdict?" — get_market_intel market=northern-virginia...
This record as markdown: /tools/cloud-dchub-mcp-server/get-market-intel.md
What get_market_intel does on Mcp Server
AI agents call get_market_intel 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 |
|---|---|---|---|
market | string | — | Market slug (metro), e.g. northern-virginia, dallas, frankfurt, singapore — valid slugs come from rank_markets / get_market_dcpi_rank |
metric | string | — | Optional single metric to focus on, e.g. vacancy, pricing, absorption, pipeline |
period | string | — | Optional time window for the metric, e.g. ttm, 12mo, ytd |
compare_to | string | — | Optional second market slug to compare against, e.g. dallas |
Parameters from the server's own tool schema.
Why get_market_intel is rated Low
This tool performs data retrieval and querying across 300+ data-center markets. It reads pre-computed analytics and market metrics without creating, modifying, deleting, or executing operations. The parameters are simple lookup identifiers with no capability to alter underlying data or trigger downstream actions.
From the tool's definition Tool retrieves market intelligence data: vacancy rates, pricing, supply pipeline, operator information, and DCPI verdicts. Returns structured data with no parameters that modify state (market_slug is a lookup key).
Attacks that exploit this kind of access
The rule that runs get_market_intel 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 get_market_intel, this is the rule to start with:
get_market_intel 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 get_market_intel call is checked against it from then on.
Questions about get_market_intel
Use when a user asks about ONE data-center market — vacancy, capacity pricing, supply pipeline, dominant operators, YoY growth — across any of 300+ markets. Example: "What is Northern Virginia's vacancy rate, $/MW-day pricing, and current DCPI verdict?" — get_market_intel market=northern-virginia. Params: market is the market_slug (e.g. "northern-virginia", "dallas", "phoenix", "frankfurt", "tokyo", "singapore"). Returns: {market, country, capacity_mw_total, capacity_mw_under_construction, vacancy_pct, absorption_mw_ttm, price_per_mw_day_usd, yoy_growth_pct, dominant_operators[], dcpi_verdict (BUILD/CAUTION/AVOID), composite_score, last_updated}. Do NOT use to rank multiple markets (use rank_markets) or for a single facility (use get_facility). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_market_intel accepts 4 parameters: market, metric, period, compare_to. 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 get_market_intel: 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.
get_market_intel 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 get_market_intel 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 get_market_intel. 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.
get_market_intel 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