get_intelligence_index
Real-time composite market health score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30d trend direction, and underlying component scores. Try: g...
This record as markdown: /tools/cloud-dchub-mcp-server/get-intelligence-index.md
What get_intelligence_index does on Mcp Server
AI agents call get_intelligence_index 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.
Why get_intelligence_index is rated Low
get_intelligence_index performs data retrieval and aggregation only—it queries an index, computes a composite score from existing metrics, and returns results. There are no side effects, data modifications, code execution, deletions, or financial operations. The tool has minimal blast radius if misused by an AI agent, as it only exposes market intelligence data already aggregated for public or authorized access.
From the tool's definition Tool retrieves and returns real-time composite market health scores, percentile ranks, trend directions, and component scores with no modification of underlying data.
Attacks that exploit this kind of access
The rule that runs get_intelligence_index 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_intelligence_index, this is the rule to start with:
get_intelligence_index 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_intelligence_index call is checked against it from then on.
Questions about get_intelligence_index
Real-time composite market health score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30d trend direction, and underlying component scores. Try: get_intelligence_index market=northern-virginia. Returns ONE composite health number for a market; do NOT use for the full market metric set (use get_market_intel) or to rank multiple markets (use rank_markets). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for get_intelligence_index: 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_intelligence_index 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_intelligence_index 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_intelligence_index. 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_intelligence_index 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