gridpulse

SERVERPulsenetwork SOURCEhttps://pulse.theaslangroupllc.com/api/mcp

High RISK CLASS

Category Execute

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/gridpulse.md

WHAT IT DOES

What gridpulse does on Pulsenetwork

AI agents invoke gridpulse to trigger actions in Pulsenetwork. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`mw`	string	—	Load in MW — scales the absolute CO2 and EUR savings
`zip`	string	—	US ZIP code (preferred)
`goal`	string	—	What to optimise. cost and blend require a region with a published day-ahead price series (DE, FR, BE and other bidding zones).
`lang`	string	—	Response language (default en)
`hours`	string	—	Forward window in hours, 1-48
`miles`	string	—	Annual miles (1,000-100,000)
`state`	string	—	2-letter US state code (TX, CA, NY, etc.; default: US)
`action`	string	Yes	Which endpoint to call. Options: carbon-intensity \| compute-window \| prices \| grid \| renewable \| natural-gas \| forecast \| ev-cost \| solar \| appliance \| battery
`has_ev`	string	—	true if household has an EV (major TOU savings driver)
`region`	string	—	UK \| a GB DNO region (london, north-scotland, …) \| DE FR NL BE AT ES IT NO
`utility`	string	—	Utility name (e.g., PGE, SCE, ConEd) for utility-specific TOU plans
`location`	string	—	City, State or place name

Parameters from the server's own tool schema.

RISK

Why gridpulse is rated High

gridpulse triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsHigh parameter count (22 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gridpulse safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gridpulse, this is the rule to start with:

gridpulse Rate-limited

gridpulse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gridpulse": {
      "limits": [
        {
          "counter": "gridpulse_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pulsenetwork, apply this rule, and every gridpulse call is checked against it from then on.

FAQ

Questions about gridpulse

What does the gridpulse tool do? +

GridPulse: Global energy grid intelligence API. NREL + EIA + Open-Meteo data synthesis. Home solar feasibility, electricity rate analysis, time-of-use optimization, EV charging cost modeling, battery storage ROI Coverage: Global Endpoints: • carbon-intensity ($0.01): Live grid carbon intensity now + forward curve (GB regions + 8 EU countries) • compute-window ($0.25): Find the optimal 48h window to run a compute workload (carbon or cost) • prices ($0.08): Electricity prices by state • grid ($0.08): Power grid status by region • renewable ($0.08): Renewable energy profile by state • natural-gas ($0.08): Henry Hub natural gas briefing • forecast ($0.10): 90-day energy forecast by state • ev-cost ($0.08): EV charging cost vs gasoline • solar ($0.10): Home solar feasibility analysis • appliance ($0.05): Home appliance energy cost calculator • battery ($0.10): Home battery storage analysis • carbon ($0.05): Household electricity carbon footprint • community-solar ($0.08): Community solar enrollment by ZIP code • tou ($0.08): Time-of-use rate optimization. It is categorised as a Execute tool in the Pulsenetwork MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does gridpulse accept? +

gridpulse accepts 12 parameters: mw, zip, goal, lang, hours, miles, state, action, has_ev, region, utility, location. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gridpulse? +

Register the Pulsenetwork MCP server in PolicyLayer and add a rule for gridpulse: 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 Pulsenetwork. Nothing to install.

What risk level is gridpulse? +

gridpulse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gridpulse? +

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

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

gridpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pulsenetwork, and thousands of servers like it.

This server

All 80 Pulsenetwork tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →