adw.adw_524
Returns a 0-100 per-county EV-charging build-out score for all 3,222 US counties (public station and port density, DC fast and Level 2, normalized per capita) with ev_charging_score, dcfc_ports_per_100k, l2_ports_per_100k, county_percentile, state_rank, and methodology_version. Call when the user...
This record as markdown: /tools/com-alpinedataworks-adw-intelligence-server/adw.adw-524.md
What adw.adw_524 does on AlpineDataWorks Intelligence Server
AI agents invoke adw.adw_524 to trigger actions in AlpineDataWorks Intelligence Server. 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 |
|---|---|---|---|
days | integer | — | Optional: return a daily HISTORY series of the last N days (up to 5 years of real archived data) instead of the current snapshot. History requires Gold tier; wi |
Parameters from the server's own tool schema.
Why adw.adw_524 is rated High
adw.adw_524 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.
Attacks that exploit this kind of access
The rule that runs adw.adw_524 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AlpineDataWorks Intelligence Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adw.adw_524, this is the rule to start with:
adw.adw_524 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AlpineDataWorks Intelligence Server, apply this rule, and every adw.adw_524 call is checked against it from then on.
Questions about adw.adw_524
Returns a 0-100 per-county EV-charging build-out score for all 3,222 US counties (public station and port density, DC fast and Level 2, normalized per capita) with ev_charging_score, dcfc_ports_per_100k, l2_ports_per_100k, county_percentile, state_rank, and methodology_version. Call when the user asks about local EV-charging build-out, charging deserts, or county EV readiness, or when timing charger deployment, fleet electrification, or site-selection decisions. Updates: on source cadence. It is categorised as a Execute tool in the AlpineDataWorks Intelligence Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
adw.adw_524 accepts 1 parameter: days. The full parameter table on this page comes from the server's own tool schema.
Register the AlpineDataWorks Intelligence Server MCP server in PolicyLayer and add a rule for adw.adw_524: 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 AlpineDataWorks Intelligence Server. Nothing to install.
adw.adw_524 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adw.adw_524 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 adw.adw_524. 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.
adw.adw_524 is provided by the AlpineDataWorks Intelligence Server MCP server (https://api.alpinedataworks.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AlpineDataWorks Intelligence Server, and thousands of servers like it.
Across the catalogue