get_grid_data

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/get-grid-data.md

WHAT IT DOES

What get_grid_data does on Mcp Server

AI agents call get_grid_data 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
`iso`	string	—	Grid code (required): a US ISO (ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE), TVA, BPA, a utility BA or city (AZPS, PHOENIX), or a non-US grid (IESO, AESO, HYDRO
`metric`	string	—	Optional metric focus, e.g. fuel_mix, demand, demand_curve
`period`	string	—	Optional time window for the metric, e.g. 24h
`mpp_pay`	boolean	—	Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has expli
`mpp_credential`	string	—	Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approv

Parameters from the server's own tool schema.

RISK

Why get_grid_data is rated Low

Tool queries and returns grid data without side effects, creating, modifying, or executing operations.

From the tool's definition retrieves live electricity grid data, power demand, fuel mix; no modifications or actions

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_grid_data 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_grid_data, this is the rule to start with:

get_grid_data Allowed

get_grid_data 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": {
    "get_grid_data": {}
  }
}

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 get_grid_data call is checked against it from then on.

FAQ

Questions about get_grid_data

What does the get_grid_data tool do? +

Use this when the user asks for live electricity grid data (power demand, fuel mix) for one grid: the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), TVA, BPA, 40+ US utility balancing authorities (e.g. AZPS, SOCO, DUK, FPL, or a city: PHOENIX, ATLANTA), Canada (IESO, AESO, HYDROQUEBEC), Great Britain (NGESO), any ENTSO-E bidding zone (EU_DE_LU, EU_FR, EU_NL ...), Taiwan (TAIPOWER), Japan (OCCTO), South Korea (KEPCO-KR), Brazil (ONS), Australia (AEMO) or Singapore (EMA). US ISOs and EIA regions return EIA hourly fuel mix, demand and the 24h curve; other grids return each feed's newest reading per metric, each with its own timestamp. Raw telemetry for one grid; do NOT use for power-availability, time-to-power or interconnection-queue analysis (use get_grid_intelligence), nor for retail/gas pricing (use get_energy_prices). To rank many grids at once use get_grid_scoreboard. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_grid_data accept? +

get_grid_data accepts 5 parameters: iso, metric, period, mpp_pay, mpp_credential. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_grid_data? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for get_grid_data: 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 get_grid_data? +

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

Can I rate-limit get_grid_data? +

Yes. Add a rate_limit block to the get_grid_data 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 get_grid_data completely? +

Set action: deny in the PolicyLayer policy for get_grid_data. 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 get_grid_data? +

get_grid_data 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 94 Mcp Server tools →

Across the catalogue

get_customer_data on 08-AI-Business-Agent →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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