adw.adw_557
Returns a 0-100 US severe-weather warning-pressure score (every active NWS watch/warning/advisory weighted Extreme=4 to Minor=1 on a saturating scale, refreshed hourly) with trend, confidence, top_drivers by event type, severity breakdown, states affected, and recent Extreme/Severe alerts. Call w...
This record as markdown: /tools/com-alpinedataworks-adw-intelligence-server/adw.adw-557.md
What adw.adw_557 does on AlpineDataWorks Intelligence Server
AI agents invoke adw.adw_557 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_557 is rated High
adw.adw_557 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs adw.adw_557 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_557, this is the rule to start with:
adw.adw_557 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_557 call is checked against it from then on.
Questions about adw.adw_557
Returns a 0-100 US severe-weather warning-pressure score (every active NWS watch/warning/advisory weighted Extreme=4 to Minor=1 on a saturating scale, refreshed hourly) with trend, confidence, top_drivers by event type, severity breakdown, states affected, and recent Extreme/Severe alerts. Call when the user asks how severe the current US weather-warning load is, which states are under alerts, or about storm severity, or when timing logistics holds, staffing surges, or event go/no-go decisions. Updates: hourly. 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_557 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_557: 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_557 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_557 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_557. 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_557 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