nrel_solar_resource
Annual and monthly solar resource data (Direct Normal Irradiance, Global Horizontal Irradiance, Latitude-Tilt Irradiance) for a location. Useful for site evaluation before sizing a solar system.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nrel-solar-resource.md
What nrel_solar_resource does on Livedatalink
AI agents call nrel_solar_resource to retrieve information from Livedatalink 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 |
|---|---|---|---|
lat | number | — | Latitude in decimal degrees. Use with lon as alternative to address. |
lon | number | — | Longitude in decimal degrees. Use with lat as alternative to address. |
address | string | — | Street address, city/state, or place name. Either address OR lat+lon required. |
Parameters from the server's own tool schema.
Why nrel_solar_resource is rated Low
This is a pure data retrieval tool that queries solar resource information for site evaluation purposes. It has no side effects, does not modify or delete data, does not execute code or external operations, and does not involve financial transactions. The sole function is to fetch and return solar radiation metrics for a given location, which is characteristic of a Read operation with minimal risk.
From the tool's definition Tool retrieves 'Annual and monthly solar resource data' for location-based queries. Operations are limited to data retrieval (DNI, GHI, Latitude-Tilt Irradiance metrics) with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs nrel_solar_resource safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nrel_solar_resource, this is the rule to start with:
nrel_solar_resource 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 Livedatalink, apply this rule, and every nrel_solar_resource call is checked against it from then on.
Questions about nrel_solar_resource
Annual and monthly solar resource data (Direct Normal Irradiance, Global Horizontal Irradiance, Latitude-Tilt Irradiance) for a location. Useful for site evaluation before sizing a solar system. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nrel_solar_resource accepts 3 parameters: lat, lon, address. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for nrel_solar_resource: 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 Livedatalink. Nothing to install.
nrel_solar_resource 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 nrel_solar_resource 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 nrel_solar_resource. 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.
nrel_solar_resource is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue