grid_transition_radar
Use this when the user asks where new grid headroom for data centers is emerging. Returns the US markets + ISOs with the strongest near-term emergence signal (BUILD verdict + excess-power headroom + short time-to-power), an ISO rollup, and a grid-headroom leaderboard. With a paid key, also the tr...
This record as markdown: /tools/cloud-dchub-mcp-server/grid-transition-radar.md
What grid_transition_radar does on Mcp Server
AI agents call grid_transition_radar 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 |
|---|---|---|---|
limit | integer | — | Number of emerging markets to return |
max_months | integer | — | Maximum acceptable time-to-power in months for the emergence signal, 1-120, e.g. 24 |
Parameters from the server's own tool schema.
Why grid_transition_radar is rated Low
Queries and returns analytical grid data; no write or destructive side effects.
From the tool's definition Returns US markets + ISOs with strongest near-term emergence signal
Attacks that exploit this kind of access
The rule that runs grid_transition_radar 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 grid_transition_radar, this is the rule to start with:
grid_transition_radar 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 grid_transition_radar call is checked against it from then on.
Questions about grid_transition_radar
Use this when the user asks where new grid headroom for data centers is emerging. Returns the US markets + ISOs with the strongest near-term emergence signal (BUILD verdict + excess-power headroom + short time-to-power), an ISO rollup, and a grid-headroom leaderboard. With a paid key, also the transition thesis: which ISO is opening up and why. The predictive counter to retrospective "where capacity landed" reports. Answers "where should I be looking next", "which market is about to become buildable". Try: grid_transition_radar max_months=24. Do NOT use for the current ISO queue snapshot (use get_interconnection_queue) or a present-day market ranking (use rank_markets); this is the forward-looking emergence radar. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
grid_transition_radar accepts 2 parameters: limit, max_months. 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 grid_transition_radar: 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.
grid_transition_radar 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 grid_transition_radar 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 grid_transition_radar. 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.
grid_transition_radar 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