adw.adw_125
How heavy is US notifiable-disease burden?
This record as markdown: /tools/com-alpinedataworks-adw-intelligence-server/adw.adw-125.md
What adw.adw_125 does on AlpineDataWorks Intelligence Server
AI agents call adw.adw_125 to retrieve information from AlpineDataWorks Intelligence 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 |
|---|---|---|---|
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_125 is rated Low
This is a data retrieval tool that answers questions about US public health metrics (notifiable disease burden). It performs no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. It is a Read operation in the read-only intelligence/analytics category typical of the AlpineDataWorks Intelligence Server.
From the tool's definition Tool name 'adw.adw_125' with description 'How heavy is US notifiable-disease burden?' indicates a query that retrieves epidemiological data about disease burden.
Attacks that exploit this kind of access
The rule that runs adw.adw_125 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_125, this is the rule to start with:
adw.adw_125 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 AlpineDataWorks Intelligence Server, apply this rule, and every adw.adw_125 call is checked against it from then on.
Questions about adw.adw_125
How heavy is US notifiable-disease burden?. It is categorised as a Read tool in the AlpineDataWorks Intelligence Server MCP Server, which means it retrieves data without modifying state.
adw.adw_125 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_125: 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_125 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 adw.adw_125 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_125. 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_125 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